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

From: Lucas Brito <lucas75(at)gmail(dot)com>
To: Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>
Cc: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5
Date: 2009-05-11 09:38:44
Message-ID: cccdaefb0905110238j1d3124dfn73c6dab5c63b02fb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/5/11 Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>

> the thing with statement_timeout is a little bit of an issue.
> you could do:
> SET statement_timeout TO ...;
> SELECT FOR UPDATE ...
> SET statement_timeout TO default;
>

Why not extend the "SET" instruction to allow configuration parameters to be
set only in the duration of the transaction or the next "n" commands?

--
Lucas Brito

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2009-05-11 09:48:18 Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5
Previous Message Hans-Juergen Schoenig 2009-05-11 09:18:43 Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5