On Mon, Jan 11, 2016 at 1:39 PM, Jim Nasby <Jim.Nasby@xxxxxxxxxxxxxx> wrote:
Okay, I'll go visit the pgbouncer guys and see if they can shed any light. Thanks.
On 1/11/16 1:32 PM, Skarsol wrote:
pgbouncer (S-0x17fd780 entries):
2016-01-11 12:21:46.600 32905 LOG S-0x17fd780:
edi01/editor@127.0.0.1:6432 <http://editor@127.0.0.1:6432> closing
because: server idle timeout (age=612)
2016-01-11 12:23:28.142 32905 LOG S-0x17fd780:
edi01/editor@127.0.0.1:6432 <http://editor@127.0.0.1:6432> new
connection to server
2016-01-11 12:23:28.143 32905 LOG S-0x17fd780:
edi01/editor@127.0.0.1:6432 <http://editor@127.0.0.1:6432> closing
because: sent cancel req (age=0)
2016-01-11 12:26:31.510 32905 LOG S-0x17fd780:
edi01/editor@127.0.0.1:6432 <http://editor@127.0.0.1:6432> new
connection to server
This makes me think there's a race condition in pgBouncer, or that their logging is just confusing.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
Okay, I'll go visit the pgbouncer guys and see if they can shed any light. Thanks.