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

Re: Trapping QUERY_CANCELED: yes, no, maybe?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Trapping QUERY_CANCELED: yes, no, maybe?
Date: 2004-08-01 01:24:33
Message-ID: 9532.1091323473@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> You are asking if a funciton itself might want to set query cancel and
> catch the cancel and do something else?

Exactly.  There's a proof-of-concept test at the bottom of
regress/sql/plpgsql.sql, wherein a function gets control back
from a query that would have run for an unreasonably long time.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-08-01 01:27:17
Subject: Re: Version Numbering -- The great debate
Previous:From: Bruce MomjianDate: 2004-08-01 01:20:25
Subject: Re: Trapping QUERY_CANCELED: yes, no, maybe?

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