Re: Error reporting when hitting shared memory limits -

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Pete Leonard <pete(at)hero(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error reporting when hitting shared memory limits -
Date: 2001-08-25 10:16:16
Message-ID: Pine.LNX.4.30.0108251205520.702-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tsukaeru.net Webmaster 2001-08-25 12:00:50 Re: Backend message type 0x44 arrived while idle
Previous Message Tom Lane 2001-08-25 04:37:09 Re: backend dies on my aggregate function in 7.1.2