Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f34G7U849470 for ; Wed, 4 Apr 2001 12:07:30 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f34G7Hw10903; Wed, 4 Apr 2001 12:07:17 -0400 (EDT) To: "Graham Vickrage" cc: "Postgres SQL" Subject: Re: Strategy for unlocking query In-reply-to: References: Comments: In-reply-to "Graham Vickrage" message dated "Wed, 04 Apr 2001 16:34:54 +0100" Date: Wed, 04 Apr 2001 12:07:17 -0400 Message-ID: <10900.986400437@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/49 X-Sequence-Number: 2388 "Graham Vickrage" writes: > I have just done a rather large transaction via a telnet/psql session which > executed OK. The problem occured when the telnet session timed out before I > could commit the rows. > This must have locked the rows in question because when I tried to vacuum > the table it just hung. Probably the backend process was still there and didn't yet realize that the client connection had died. It would notice eventually, but I think the timeout involved is typically an hour or so (this is determined by the TCP protocols and isn't under our control). > What is the best way of dealing with this problem as I ended up stopping and > restarting the postmaster? It would've been sufficient to find and SIGTERM the individual backend from the lost session. regards, tom lane