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.
On 11 May 2009, at 10:26, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>
> hello everybody,
> i would like to propose an extension to our SELECT FOR UPDATE
> 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:
> informix should behave pretty much the same way.
> are there any arguments from hackers' side against this feature?
> many thanks,
> 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:
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2009-05-11 08:02:17|
|Subject: Re: [PATCH] Automatic client certificate selection support
for libpq v1|
|Previous:||From: Peter Eisentraut||Date: 2009-05-11 07:53:08|
|Subject: Re: [PATCH] Automatic client certificate selection support for libpq v1|