Skip site navigation (1) Skip section navigation (2)

Re: could not fork new process for connection: Cannot allocate memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: Pavel Veretennikov <vermut(at)kid(dot)lv>,"pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: could not fork new process for connection: Cannot allocate memory
Date: 2004-07-26 05:24:04
Message-ID: 19182.1090819444@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Gaetano Mendola <mendola(at)bigfoot(dot)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

In response to

pgsql-admin by date

Next:From: Nigel BishopDate: 2004-07-26 09:02:32
Subject: FW: Error in logfile on DB startup
Previous:From: SteveDate: 2004-07-26 01:46:22
Subject: Re: Utilizing multiple disks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group