Re: Error reporting when hitting shared memory limits -

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Error reporting when hitting shared memory limits -
Дата
Msg-id Pine.LNX.4.30.0108251205520.702-100000@peter.localdomain
обсуждение исходный текст
Ответ на Error reporting when hitting shared memory limits -  (Pete Leonard <pete@hero.com>)
Ответы Re: Error reporting when hitting shared memory limits -  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Pete Leonard writes:

> If you start up Postgres (7.1.2) and specify a number of buffers greater
> than what SHMMAX can provide, you get a nice, useful error message,
> detailing what's wrong, and with suggestions on how to fix it.
>
> If you start up Postgres and specify a number of buffers that falls within
> the limits of SHMMAX, but exceeds SHMALL, you get an error message like
> this:
>
> IpcMemoryCreate: shmget(key=5432001, size=29868032, 03600) failed: Cannot allocate memory

The FreeBSD shmget(2) man page does not document this error (ENOMEM).
However, the Linux shmget(2) page says

       ENOMEM      is returned if no memory  could  be  allocated
                   for segment overhead.

which probably means to raise SHMALL.

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: backend dies on my aggregate function in 7.1.2
Следующее
От: "Tsukaeru.net Webmaster"
Дата:
Сообщение: Re: Backend message type 0x44 arrived while idle