Re: transaction idle timeout in 7.4.5 and 8.0.0beta2

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Szima G?bor <sygma(at)axelero(dot)hu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: transaction idle timeout in 7.4.5 and 8.0.0beta2
Date: 2004-09-18 17:26:03
Message-ID: 20040918172603.GB71269@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Wheeler 2004-09-18 17:28:54 Re: libpq and prepared statements progress for 8.0
Previous Message Tom Lane 2004-09-18 17:01:42 Re: tweaking MemSet() performance - 7.4.5