Skip site navigation (1) Skip section navigation (2)

Re: timeout implementation issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: timeout implementation issues
Date: 2002-03-30 17:59:03
Message-ID: 2103.1017511143@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com> writes:
> I definitely agree that implementing it in the backend would be the best
> plan, if it's feasible. I just can't figure out how to pass information
> back to the driver that the request has been cancelled (and that, in
> JDBC's case, a SQLException should be thrown). Any thoughts about that?

Why would this be any different from a cancel-signal-instigated abort?
You'd be reporting elog(ERROR) in any case.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-03-30 18:17:19
Subject: PGSTAT start failure probably shouldn't disable Postgres
Previous:From: Greg CopelandDate: 2002-03-30 15:59:11
Subject: Re: Posix AIO in new Red Hat Linux

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group