Re: [GENERAL] Auto-timeout on all queries

From: Peter Eisentraut <peter(at)pathwaynet(dot)com>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Bob Kruger <bkruger(at)mindspring(dot)com>, PostgreSQL-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: [GENERAL] Auto-timeout on all queries
Date: 1999-07-06 22:28:56
Message-ID: Pine.LNX.4.10.9907061826500.518-100000@saxony.pathwaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 5 Jul 1999, Bruce Momjian wrote:

> > I would like to make one small request for future releases. Is there a
> > setup parameter that could be enabled that would put a timeout for a query
> > that runs too long or endangers the integrity of the system? With the
> > systems that I use, there are times that queries are entered that contain
> > errors or run so long that they eventually cause a system crash. It would
> > be most helpful if a timeout limit on queries could be enabled that would
> > stop a query after so much time and release the resources back to the system.
>
> Does anyone thing this would be a nice feature? We can easily do it
> with alarm()/elog(), but I want to know if it would be valuable.

Oh yeah!

Time out in minutes, "time" out in tuples, all with an instructive error
message if exceeded. How about

SET TIMEOUT '5 min';
SET TUPLE LIMIT 10000;

If you can really "easily" do it, I say go for it.

--
Peter Eisentraut
PathWay Computing, Inc.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 1999-07-06 22:38:04 Re: Fw: Re[2]: [GENERAL] Joins and links
Previous Message Michael J Davis 1999-07-06 21:11:43 RE: [GENERAL] Finding an empty field