Re: Plans for 8.2? - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: Plans for 8.2?
Date
Msg-id 20060113214048.GU9017@pervasive.com
Whole thread Raw
In response to Re: Plans for 8.2?  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Plans for 8.2?  (Michael Fuhr <mike@fuhr.org>)
List pgsql-general
On Fri, Jan 13, 2006 at 01:59:19AM -0700, Michael Fuhr wrote:
> On Fri, Jan 13, 2006 at 01:49:02AM -0700, Michael Fuhr wrote:
> > On Fri, Jan 13, 2006 at 09:30:22AM +0100, H.J. Sanders wrote:
> > > Just one request that would make the transition from another
> > > great database to PostgreSQL a lot easier:
> > >
> > > SET LOCK MODE TO WAIT n
> > >
> > > n = the max.time in second to wait.
> >
> > Will statement_timeout suffice?
>
> (I'm not implying that statement_timeout is equivalent, I'm just
> wondering if you might be able to use it in certain circumstances.)

It strikes me that if we had a way to abort a statement on another
backend, you could abort anything that's been waiting more than x
seconds for a lock via an external process watching pg_locks. Of course,
that would be much more cumbersom than SET LOCK MODE TO WAIT n...
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Plans for 8.2?
Next
From: Jaime Casanova
Date:
Subject: Re: Plans for 8.2?