Re: icps, shmmax and shmall - Shared Memory tuning

Поиск
Список
Период
Сортировка
От dorian dorian
Тема Re: icps, shmmax and shmall - Shared Memory tuning
Дата
Msg-id 20020501184955.56859.qmail@web14806.mail.yahoo.com
обсуждение исходный текст
Ответ на Re: icps, shmmax and shmall - Shared Memory tuning  (Martijn van Oosterhout <kleptog@svana.org>)
Список pgsql-general
So to return to my initial question.. Here's a summary
of the error message and my settings after the crash -

May  1 13:24:42 mito logger: IpcMemoryCreate:
shmget(key=5432001, size=140361728, 03600) failed:
Invalid argument
May  1 13:24:42 mito logger: This error usually means
that PostgreSQL's request for a shared memory
May  1 13:24:42 mito logger: segment exceeded your
kernel's SHMMAX parameter.  You can either
May  1 13:24:42 mito logger: reduce the request size
or reconfigure the kernel with larger SHMMAX.
May  1 13:24:42 mito logger: To reduce the request
size (currently 140361728 bytes), reduce
May  1 13:24:42 mito logger: PostgreSQL's
shared_buffers parameter (currently 16384) and/or
May  1 13:24:42 mito logger: its max_connections
parameter (currently 256).

# sysctl kernel.shmmax
kernel.shmmax = 201326592

# sysctl kernel.shmall
kernel.shmall = 201326592

I've got 512MB RAM - what am I doing wrong? Postgres
consistently crashes (and subsequently takes the
machine down) on any heavy abuse.

Any other settings I should be looking at?


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Count(*) Question
Следующее
От: elein
Дата:
Сообщение: explain and explain analyze with functions