Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
От | John R Pierce |
---|---|
Тема | Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover |
Дата | |
Msg-id | 571792C0.3060503@hogranch.com обсуждение исходный текст |
Ответ на | Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #14101: Postgres Service Crashes With Memory Error And
Does Not Recover
|
Список | 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 по дате отправления: