Re: Determining server load

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 show plenty 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 looked the *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(at)database), I believe you CAN track the max connections via
pgbouncer's pool stats.

--
john r pierce, recycling bits in santa cruz