From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: What is happening on buildfarm member baiji? |
Date: | 2007-05-14 15:38:24 |
Message-ID: | 87sl9zbekv.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Um, you're right, I hadn't done the test properly. If I have an open
> psql session across TCP and do pg_ctl stop -m fast, then I can't
> start a new postmaster until the socket goes out of CLOSE_WAIT state.
> Which, if I just leave the psql session sit there, seems to mean
> "indefinitely" ... so it's even worse than just a TCP timeout.
That's still not quite right. Are you running the client and server on the
same machine? Shutting down the server should put its connection in FIN_WAIT1
which would immediately go to FIN_WAIT2 if psql is still reachable. I think
the connection you're seeing in CLOSE_WAIT is the client's end of the
connection.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-14 15:43:30 | Re: What is happening on buildfarm member baiji? |
Previous Message | Tom Lane | 2007-05-14 15:28:40 | Re: What is happening on buildfarm member baiji? |