[#1011195] Log when pool_size reached

View Trackers | Feature Requests | Download .csv | Monitor

Date:
2012-05-18 06:17
Priority:
3
State:
Open
Submitted by:
Haw Loeung (hloeung)
Assigned to:
Nobody (None)
Category:
Group:
Summary:
Log when pool_size reached

Detailed description
Hi,

We had an issue where DB connections were failing and nothing was showing in the pgbouncer logs. As it turned out, it seemed to be hitting the default_pool_size of 20.

Is there any chance of adding extra logging so it'll be more obvious when this limit is hit?


Thanks,

Haw

Followup

Message
Date: 2012-05-29 21:17
Sender: Marko Kreen

Hitting the ceiling is normal, thats the point of it - to flatten peaks.

And we actually have such logging, if you have reserve_pool activated. Then you get a warning each time new connection is taken from reserve pool.

So the question is - should we log anything, when reserve pool is not activated? How to rate-limit such warnings?
Basically, the pool size should not be that big that it's never hit. So how should logging be performed?

Currently it's seems simplest to say - do use reserve_pool if you want such logging.
Date: 2012-05-18 06:43
Sender: Haw Loeung

Btw, I have the following settings:

logfile = /var/log/postgresql/pgbouncer.log
log_connections = 1
log_disconnections = 1
log_pooler_errors = 1

grep 'too many' pgbouncer.log returns nothing. pgbouncer-
1.3.1

Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge