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

Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5

From: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5
Date: 2009-05-11 07:59:54
Message-ID: CF181E6B-BBF9-4F28-AAEA-DC9D9BC98001@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Can't you to this today with statement_timeout? Surely you do want to  
rollback the whole transaction or at least the subtransaction if you  
have error handling.

-- 
Greg


On 11 May 2009, at 10:26, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>  
wrote:

> hello everybody,
>
> i would like to propose an extension to our SELECT FOR UPDATE  
> mechanism.
> especially in web applications it can be extremely useful to have  
> the chance to terminate a lock after a given timeframe.
> i would like to add this functionality to PostgreSQL 8.5.
>
> the oracle syntax is quite clear and easy to use here:
>
> http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_10002.htm#i2126016
>
> informix should behave pretty much the same way.
> are there any arguments from hackers' side against this feature?
>
>   many thanks,
>
>      hans
>
> -- 
> Cybertec Schönig & Schönig GmbH
> Professional PostgreSQL Consulting, Support, Training
> Gröhrmühlgasse 26, A-2700 Wiener Neustadt
> Web: www.postgresql-support.de
>
>
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2009-05-11 08:02:17
Subject: Re: [PATCH] Automatic client certificate selection support for libpq v1
Previous:From: Peter EisentrautDate: 2009-05-11 07:53:08
Subject: Re: [PATCH] Automatic client certificate selection support for libpq v1

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