Re: 8.2 beta blockers - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: 8.2 beta blockers
Date
Msg-id b42b73150609181330r2b86428cq6fb244a3141392f9@mail.gmail.com
Whole thread Raw
In response to Re: 8.2 beta blockers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.2 beta blockers  (Josh Berkus <josh@agliodbs.com>)
Re: 8.2 beta blockers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/18/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Merlin Moncure" <mmoncure@gmail.com> writes:
> > yes, i can explain it in detail, and am willing to kick in some
> > documentation.
>
> Ah-hah, you're on the hook for docs then ;-).

sure no problem.  the prototypes you suggested are imo the way to go,
with two small considerations:

is it worth considering using the  oid type instead of int4 since the
'locktag' fields are unsigned?
also, the userlocks raised a warning if you tried to release a
non-existing lock.  should that stay or go?

> As far as the PR material goes, something like "advisory locks
> incorporated into core" would be OK, but don't make it sound like
> there was nothing there before ...

ok, thats a good compromise.

merlin


pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: Re: An Idea for OID conflicts
Next
From: Josh Berkus
Date:
Subject: Re: 8.2 beta blockers