Re: Trapping QUERY_CANCELED: yes, no, maybe?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Manfred Koizar <mkoi-pg(at)aon(dot)at>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Trapping QUERY_CANCELED: yes, no, maybe?
Date: 2004-08-06 22:55:49
Message-ID: 24208.1091832949@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Manfred Koizar <mkoi-pg(at)aon(dot)at> writes:
> referring to
> | -- we assume this will take longer than 1 second:
> | select count(*) into x from tenk1 a, tenk1 b, tenk1 c;

> Maybe
> SELECT sleep('0:0:2'::interval);
> as used in regress/sql/stats.sql is a better way to ensure that the
> query takes longer than one second?

You think there's a serious risk of failure there ;-) ?

By my count the query will try to generate one trillion join rows.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2004-08-06 23:15:00 Re: Trapping QUERY_CANCELED: yes, no, maybe?
Previous Message Manfred Koizar 2004-08-06 22:20:08 Re: Trapping QUERY_CANCELED: yes, no, maybe?