Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 - Mailing list pgsql-hackers

From Jeroen T. Vermeulen
Subject Re: transaction idle timeout in 7.4.5 and 8.0.0beta2
Date
Msg-id 20040918172603.GB71269@xs4all.nl
Whole thread Raw
In response to Re: transaction idle timeout in 7.4.5 and 8.0.0beta2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: transaction idle timeout in 7.4.5 and 8.0.0beta2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Sep 18, 2004 at 12:43:05PM -0400, Tom Lane wrote:
> I don't see any reason for guesswork.  Remember the PID of the backend
> you were connected to.  On reconnect, look in pg_stat_activity to see if
> that backend is still alive; if so, sleep till it's not.  Then check to
> see if your transaction committed or not.  No need for anything so
> dangerous as a timeout.

Looks like that only works if stats_command_string is set (and backend
version is at least 7.2), correct?  I couldn't find this table in the
online documentation, but can I assume that the query will have finished
executing (whether for good or for bad) when its current_query is either
empty or null?


Jeroen



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tweaking MemSet() performance - 7.4.5
Next
From: David Wheeler
Date:
Subject: Re: libpq and prepared statements progress for 8.0