Re: Proposal: String key space for advisory locks

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: Proposal: String key space for advisory locks
Дата
Msg-id b42b73150910270649r59304f56h8501b6e31a780d4a@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Proposal: String key space for advisory locks  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Proposal: String key space for advisory locks  (Josh Berkus <josh@agliodbs.com>)
Список 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 по дате отправления:

Предыдущее
От: Kenneth Marshall
Дата:
Сообщение: Re: Proposal: String key space for advisory locks
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: "toast.fillfactor" is documented but not recognized?