On Wed, 2006-05-24 at 14:00, Tom Lane wrote:
> "Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> > You can (at least on linux, I assume it's the same for BSD) set the
> > "keepalive" flag of a connection. This results in empty packets being
> > sent every 30 seconds or so, and the connection is rep
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> You can (at least on linux, I assume it's the same for BSD) set the
> "keepalive" flag of a connection. This results in empty packets being
> sent every 30 seconds or so, and the connection is reported to be dead
> if no ACK is received within a tim
Richard Huxton wrote:
Gavin Hamill wrote:
Hullo :)
We have pg 8.1.3 and for whatever reason (network blips, poor pooling
on behalf of the client, etc.) we sometimes see a large number
(dozens) of old connections in the idle state which never get reused.
They should expire based on your TCP
Gavin Hamill wrote:
Hullo :)
We have pg 8.1.3 and for whatever reason (network blips, poor pooling on
behalf of the client, etc.) we sometimes see a large number (dozens) of
old connections in the idle state which never get reused.
They should expire based on your TCP/IP settings. It's a TC
Hello,
We have pg 8.1.3 and for whatever reason (network blips, poor pooling on
behalf of the client, etc.) we sometimes see a large number (dozens) of
old connections in the idle state which never get reused.
It seems that I have more or less the same problem. Sometimes I see in
`ps aux` lots
Hullo :)
We have pg 8.1.3 and for whatever reason (network blips, poor pooling on
behalf of the client, etc.) we sometimes see a large number (dozens) of
old connections in the idle state which never get reused.
Is there a function in postgres similar to MySQL's 'wait_timeout' which
automat
