Re: timeout implementation issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: timeout implementation issues
Date
Msg-id 200204021939.g32Jd8R14545@candle.pha.pa.us
Whole thread Raw
In response to Re: timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
List pgsql-hackers
Jessica Perry Hekman wrote:
> On Tue, 2 Apr 2002, Bruce Momjian wrote:
> 
> >     BEGIN WORK;
> >     query;
> >     SET statement_timeout = 4;
> >     query;
> >     SET statement_timeout = 0;
> >     query;
> >     COMMIT;
> >     SET statement_timeout = 0;
> > 
> > Basically, it does the reset twice, once assuming the transaction
> > doesn't abort, and another assuming it does abort.  Is this something
> > that the JDBC and ODBC drivers can do automatically?
> 
> I can't speak for ODBC. Seems like in JDBC, Connection::commit() would
> call code clearing the timeout, and Statement::executeQuery() and
> executeUpdate() would do the same.

Well, then a SET variable would work fine for statement-level queries. 
Just add the part for commit/abort transaction.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Jessica Perry Hekman
Date:
Subject: Re: timeout implementation issues
Next
From: Bruce Momjian
Date:
Subject: Re: status of IPv6 Support for INET/CIDR types