Re: sequence locking - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: sequence locking
Date
Msg-id CAHyXU0xXqwnAjPnv=nyh=LTay=UV0=tqOQiypzc5da2dchrRLA@mail.gmail.com
Whole thread Raw
In response to Re: sequence locking  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: sequence locking
List pgsql-hackers
On Wed, Sep 21, 2011 at 11:51 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Andres Freund <andres@anarazel.de> wrote:
>
>> - Its impossible to emulate proper locking yourself because
>> locking is not allowed for sequences
>
>> Any arguments against allowing it again? It seems to have been
>> allowed in prehistoric times.
>
> It would be nice to allow it.  I've had to create a dummy table just
> to use for locking a sequence (by convention).

another (better?) way is advisory locks...

merlin


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Remastering using streaming only replication?
Next
From: Josh Berkus
Date:
Subject: Re: unite recovery.conf and postgresql.conf