Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nathan Mascitelli <nathanmascitelli(at)geotab(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
Date: 2016-04-20 14:09:20
Message-ID: 21783.1461161360@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Nathan Mascitelli <nathanmascitelli(at)geotab(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2016-04-20 14:31:28 Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
Previous Message John R Pierce 2016-04-20 13:54:37 Re: BUG #14103: stored function encryption