Re: timeout implementation issues

From: Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: timeout implementation issues
Date: 2002-04-02 19:17:20
Message-ID: Pine.LNX.4.21.0204021415170.11943-100000@atalanta.dynamicdiagrams.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

j

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-04-02 19:30:07 Re: Dblink and ISDN
Previous Message Bruce Momjian 2002-04-02 18:39:30 Re: timeout implementation issues