al-ow...@postgresql.org] On Behalf Of Kevin Grittner
Sent: 11 December 2015 22:13
To: Carlo Cabanilla
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] connections not getting closed on a replica
On Fri, Dec 11, 2015 at 3:37 PM, Carlo Cabanilla wrote:
> 16 cores
> a default pool size of 650, stea
On Fri, Dec 11, 2015 at 3:37 PM, Carlo Cabanilla wrote:
> 16 cores
> a default pool size of 650, steady state of 500-600 server
> connections
With so many more connections than resources to serve them, one
thing that can happen is that just by happen-stance enough processes
become busy at one t
Thanks for the reply Kevin.
> > I'm trying to figure out why we had a build up of connections on
> > our streaming replica.
>
> Seriously, from the data provided, about all I can say is "because
> you were opening them faster than you were closing them". You
> don't say how many cores or how muc
On Thu, Dec 10, 2015 at 5:13 PM, Carlo Cabanilla wrote:
> I'm trying to figure out why we had a build up of connections on
> our streaming replica.
Seriously, from the data provided, about all I can say is "because
you were opening them faster than you were closing them". You
don't say how many
Hello,
I'm trying to figure out why we had a build up of connections on our
streaming replica. We're running postgres 9.3.5 on the master and 9.3.10 on
the replica, linux 3.2.0 on both, disks in raid10. Here are some graphs to
illustrate what happened:
http://dd-pastebin.s3.amazonaws.com/carlo/p
