From: | Pete Leonard <pete(at)hero(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Error reporting when hitting shared memory limits - |
Date: | 2001-08-22 20:34:36 |
Message-ID: | Pine.LNX.4.10.10108221328320.879-100000@hero.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey folks,
Quick note - in re-compiling the kernel of the box we run Postgres on
(running FreeBSD 3.4), we goofed - SHMMAX was increased, but SHMALL was
not.
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
Needless to say, we were a little stumped at first. :)
Would it be too much to ask for a failure message along the lines of what
exceeding SHMMAX provides?
thanks,
--peter
From | Date | Subject | |
---|---|---|---|
Next Message | Johann Zuschlag | 2001-08-22 20:43:03 | Re: Comparing fixed precision to floating (no anwer) |
Previous Message | Oberpriller, Wade D. | 2001-08-22 20:23:44 | ERROR: triggered data change violation on relation "mytable" |