Postgres Pro
Downloads
Home   >   mailing lists

Re: could not fork new process for connection: Cannot allocate memory - Mailing list pgsql-admin

From Tom Lane
Subject Re: could not fork new process for connection: Cannot allocate memory
Date
Msg-id 19182.1090819444@sss.pgh.pa.us
Whole thread Raw
In response to Re: could not fork new process for connection: Cannot allocate memory  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-admin
Tree view 
Gaetano Mendola <mendola@bigfoot.com> writes:
> Pavel Veretennikov wrote:
> | What could be a problem? About 3G of shared memory is allocated to PG,
> | 850000 shared_buffers.

> I don't know what you problem can be but are you sure you need that
> *very huge* ammount of shared memory ?

Conventional wisdom is that setting shared_buffers higher than a few
tens of thousands is a bad idea, no matter how much RAM you have.
See the pgsql-performance archives.

            regards, tom lane

pgsql-admin by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: Can't increase max connections
Next
From: "Nigel Bishop"
Date:
Subject: FW: Error in logfile on DB startup