From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: timeout implementation issues |
Date: | 2002-04-09 00:45:46 |
Message-ID: | 200204090045.g390jkf19963@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hiroshi Inoue wrote:
> Bruce Momjian wrote:
> >
> > Hiroshi Inoue wrote:
> > > > > Why should the SET query_timeout = 0 command be issued
> > > > > only when the query failed ? Is it a JDBC driver's requirement
> > > > > or some applications' requirements which uses the JDBC driver ?
> > > >
> > > > They want the timeout for only the one statement, so they have to set it
> > > > to non-zero before the statement, and to zero after the statement.
> > >
> > > Does setQueryTimeout() issue a corresponding SET QUERY_TIMEOUT
> > > command immediately in the scenario ?
> >
> > Yes. If we don't make the SET rollback-able, we have to do all sorts of
> > tricks in jdbc so aborted transactions get the proper SET value.
>
> In my scenario, setQueryTimeout() only saves the timeout
> value and issues the corrsponding SET QUERY_TIMEOUT command
> immediately before each query if necessary.
Yes, we can do that, but it requires an interface like odbc or jdbc. It
is hard to use for libpq or psql.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-04-09 01:06:12 | Re: timeout implementation issues |
Previous Message | Hiroshi Inoue | 2002-04-09 00:44:01 | Re: timeout implementation issues |