X-Original-To: pgsql-sql@postgresql.org
Received: from serwer.skawsoft.com.pl (serwer.skawsoft.com.pl [213.25.37.66])
	by postgresql.org (Postfix) with ESMTP id DEDD94758C9
	for <pgsql-sql@postgresql.org>; Sat,  8 Mar 2003 17:29:41 -0500 (EST)
Received: by serwer.skawsoft.com.pl (Postfix, from userid 1000)
	id 0BD282B88F; Sat,  8 Mar 2003 23:27:13 +0100 (CET)
Date: Sat, 8 Mar 2003 23:27:13 +0100
To: Mark Mitchell <mark@lapcrew.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Cancelling Queries
Message-ID: <20030308222713.GA22866@serwer>
References: <1046993130.21247.3.camel@sql.icnfull.com>
	<20030307052705.GA5440@serwer> <3E675BDC.90703@lapcrew.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E675BDC.90703@lapcrew.com>
User-Agent: Mutt/1.3.28i
From: jasiek@klaster.net
X-Archive-Number: 200303/216
X-Sequence-Number: 12256

On Thu, Mar 06, 2003 at 08:31:56AM -0600, Mark Mitchell wrote:
> These are select queries that may have been keyed incorrectly that I 
> need to cancel. So a transaction won't help in this case.
What about setting maximum query execution time in postgresql
configuration? There are some options helpful for deadlock cases.

Regards,
Tomasz Myrta