Re: Error reporting when hitting shared memory limits - - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: Error reporting when hitting shared memory limits -
Date
Msg-id Pine.LNX.4.30.0108251205520.702-100000@peter.localdomain
Whole thread Raw
In response to Error reporting when hitting shared memory limits -  (Pete Leonard <pete@hero.com>)
Responses Re: Error reporting when hitting shared memory limits -  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: backend dies on my aggregate function in 7.1.2
Next
From: "Tsukaeru.net Webmaster"
Date:
Subject: Re: Backend message type 0x44 arrived while idle