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

Re: Proposal: String key space for advisory locks

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: String key space for advisory locks
Date: 2009-10-26 20:30:00
Message-ID: 4AE606C8.8090300@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> Why aren't you satisfied with hashtext('foo') ?

Collisions, mostly.

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

Yeah, that's a pretty hard limit.  NM, we'll have to figure out some way
around it.

--Josh Berkus


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-10-26 20:33:37
Subject: Re: Parsing config files in a directory
Previous:From: Tom LaneDate: 2009-10-26 20:21:05
Subject: Re: Anonymous Code Blocks as Lambdas?

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