"Thomas O'Connell" <tfo(at)monsterlabs(dot)com> writes:
> we've had the issue before where postgres will die under heavy load
> (meaning Apache is logging several requests per minute and stressing
> postgres, too) with the error about how probably we don't have shared
> memory configured appropriately.
Uh, which error exactly? AFAIK all the shared-memory-related messages
would only come out at postmaster startup, not during peak load. The
system is designed to ensure that those resources are all reserved
during postmaster start.
regards, tom lane