Re: Proposal: String key space for advisory locks - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Proposal: String key space for advisory locks
Date
Msg-id b42b73150910270649r59304f56h8501b6e31a780d4a@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: String key space for advisory locks  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Proposal: String key space for advisory locks
List pgsql-hackers
On Mon, Oct 26, 2009 at 4:30 PM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> Why aren't you satisfied with hashtext('foo') ?
>
> Collisions, mostly.

Why even bother with a hash function when you can just have multiple
table pull from a shared sequence?  AFAICT, this solves the OP's
problem with no downsides (I used the approach with excellent results
in a ported cobol app which had pessimistic locking requirement).

merlin


pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: Proposal: String key space for advisory locks
Next
From: Alvaro Herrera
Date:
Subject: Re: "toast.fillfactor" is documented but not recognized?