Re: sequence locking

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Andres Freund" <andres(at)anarazel(dot)de>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: sequence locking
Date: 2011-09-21 17:03:17
Message-ID: 4E79D2850200002500041551@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Wed, Sep 21, 2011 at 11:51 AM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>> Andres Freund <andres(at)anarazel(dot)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...

Not under 9.0 or earlier if you want the lock to last until the end
of the transaction. Also, the fact that advisory locks are only on
numbers, without any mechanism for mapping those to character
strings, makes them poorly suited to many tasks.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-09-21 17:03:52 Re: unite recovery.conf and postgresql.conf
Previous Message Jeff Davis 2011-09-21 17:02:32 Re: Range Types - typo + NULL string constructor