No...
- Original Message -
From: "Renato Oliveira"
To: "Reggie Euser" ;
Sent: Friday, January 29, 2010 10:15 AM
Subject: Re: [ADMIN] CentOS & PostgreSQL help re: TIME_WAIT
Do you have an F5 load balancer in front of these web servers?
Renato Oliveira
Greg Stark writes:
> On Thu, Jan 28, 2010 at 8:55 PM, Tom Lane wrote:
>> In general, sockets sitting a long time in TIME_WAIT would be a network
>> problem. That state means the user process already closed the socket
>> and the network stack is waiting for the other end to acknowledge
>> connect
On Thu, Jan 28, 2010 at 8:55 PM, Tom Lane wrote:
> In general, sockets sitting a long time in TIME_WAIT would be a network
> problem. That state means the user process already closed the socket
> and the network stack is waiting for the other end to acknowledge
> connection closure.
I think you'
] CentOS & PostgreSQL help re: TIME_WAIT
Thanks to both of you. Kevin, it's not a DoS, I'm certain; client problem,
maybe .
Tom - sorry for my confusion. I'm chasing the network/firewall possibilities
as most likely causes. PostgreSQL is running quite smoothly.
FWIW, what
Thanks to both of you. Kevin, it's not a DoS, I'm certain; client problem,
maybe .
Tom - sorry for my confusion. I'm chasing the network/firewall possibilities
as most likely causes. PostgreSQL is running quite smoothly.
FWIW, what little I know about PostgreSQL, I've picked up by using it,
Tom Lane wrote:
> In general, sockets sitting a long time in TIME_WAIT would be a
> network problem. That state means the user process already closed
> the socket and the network stack is waiting for the other end to
> acknowledge connection closure. If it's not getting the ACK then
> you have
"Reggie Euser" writes:
> Zombie PostgreSQL processes in a "TIME_WAIT" state are consuming all
> available sockets on a web server I'm running. I've Googled & RTFM'ed but am
> still stumped. Sure would appreciate any ideas.
That seems a bit confused. There's no such thing as a "process in a
TIME
Zombie PostgreSQL processes in a "TIME_WAIT" state are consuming all
available sockets on a web server I'm running. I've Googled & RTFM'ed but am
still stumped. Sure would appreciate any ideas.
I've recently migrated a PHP-based web app running against PostgreSQL from a
single server running Fre
