Skip site navigation (1) Skip section navigation (2)

Re: Proposal: String key space for advisory locks

From: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: String key space for advisory locks
Date: 2009-10-26 07:12:04
Message-ID: 20091026161204.DBB9.52131E4D@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
Christophe Pettus <xof(at)thebuild(dot)com> wrote:

> Summary:    Add a string key space to the advisory lock functionality.

Why aren't you satisfied with hashtext('foo') ?

The restriction comes from LOCKTAG struct, in which
we can use only 3 * uint32 and 1 * uint16 for lock descriptor.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center



In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2009-10-26 08:56:12
Subject: Re: Tightening binary receive functions
Previous:From: Michael PaquierDate: 2009-10-26 06:50:28
Subject: Re: [PATCH] pgbench: new feature allowing to launch shell commands

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group