Timothy Perrigo <[EMAIL PROTECTED]> writes:
> I'm getting the same error now too, although postgres was running
> without problem this morning (I updated the OS yesterday). OS X 10.3.7
> Server, PostgreSQL 8.0RC1. Basically, I did a pg_dump, stopped the
> server and then tried to start it again.
Fascinating. As far as I can tell on my machine, 10.3.7 did not change
the kernel IPC limits. So if it's not working for you guys that would
suggest that 10.3.7 added some new background usage of IPC resources,
which in combination with the PG postmaster exceeds the same-as-it-ever-
was kernel limit.
If ipcs worked then we'd have some chance of investigating this, but OS
X doesn't provide ipcs. (Thank you Apple ... not)
FWIW, my installation of PG on OS X defaults to
max_connections = 50
shared_buffers = 300
because values higher than that exceed the default kernel limits.
It looks like yours has 100/1000 --- did you hand-modify that? Or maybe
you hand-modified the kernel limits? Another possible explanation is
that the 10.3.7 update overwrote any local changes you'd made to the IPC
limits.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
