On Sep 27, 2016, at 11:16 AM, John R Pierce <pierce@hogranch.com> wrote:
>
> On 9/27/2016 12:06 PM, Israel Brewster wrote:
>> That helps for one-time stat collection, but as I mentioned in my original message, since connections may not last
long,I could be getting close to, or even hitting, my connection limit while still getting values back from those that
showplenty of connections remaining, depending on how often I checked.
>>
>> I guess what would be ideal in my mind is that whenever Postgresql logged an opened/closed connection, it also
lookedthe *total* number of open connections at that time. I don't think that's possible, however :-)
>
> if you stick pgbouncer in front of postgres (with a pool for each user@database), I believe you CAN track the max
connectionsvia pgbouncer's pool stats.
Ahh! If so, that alone would be reason enough for using pgbouncer. Thanks!
-----------------------------------------------
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general