Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
Date
Msg-id 571792C0.3060503@hogranch.com
Whole thread Raw
In response to Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
List pgsql-bugs
On 4/20/2016 7:09 AM, Tom Lane wrote:
> Nathan Mascitelli<nathanmascitelli@geotab.com>  writes:
>> >The machine has the postgres server and our application server on it. There
>> >are ​around 300 databases and typically ~1000 connections. At the time of
>> >the crash there was free RAM and disk space on the server.
> You're a braver man than I, to trust Windows with a 1000-connection
> server.  But anyway, if the backend count is that high it's far from
> surprising that you hit some Windows resource limit or other.  It's
> widely considered best practice to use a connection pooler to limit
> the number of backends to something a lot less than that, regardless
> of platform.

with 300 databases in use, a pooler would not be much help.   1000
connections is an average of 3 connections per database.





--
john r pierce, recycling bits in santa cruz

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
Next
From: hus787@gmail.com
Date:
Subject: BUG #14104: PREPARE document has a missing parameter in one of the examples