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

Re: Interrupting Cursors

From: Steve Tucknott <steve(at)retsol(dot)co(dot)uk>
To: PostGreSQL <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Interrupting Cursors
Date: 2006-05-22 17:47:20
Message-ID: 1148320041.3360.54.camel@vrsol.co.uk (view raw or flat)
Thread:
Lists: pgsql-novice
Michael,
Looks as though it may well do. I'll see if I can get the pid of the
process and give it a go.

Thanks.

On Mon, 2006-05-22 at 11:27 -0600, Michael Fuhr wrote:

> On Mon, May 22, 2006 at 06:04:46PM +0100, Steve Tucknott wrote:
> > Are there any plans to introduce the ability to 'interrupt' cursors?
> > We have some large queries that the user may have set off inadvertently,
> > and it may be handy to have the ability to send an interrupt to the
> > engine. 
> 
> Would pg_cancel_backend() work?  Or could you set statement_timeout
> to a reasonable value for certain users?
> 
> http://www.postgresql.org/docs/8.1/interactive/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL-TABLE
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-STATEMENT
> 

Regards,

Steve Tucknott
ReTSol Ltd

DDI: 01903 828769
Mobile: 0773 671 5772

In response to

Responses

pgsql-novice by date

Next:From: Michael FuhrDate: 2006-05-22 17:55:41
Subject: Re: Interrupting Cursors
Previous:From: Michael FuhrDate: 2006-05-22 17:27:27
Subject: Re: Interrupting Cursors

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