Re: 8.2 beta blockers

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, "Jim C(dot) Nasby" <jimn(at)enterprisedb(dot)com>
Subject: Re: 8.2 beta blockers
Date: 2006-09-18 20:30:10
Message-ID: b42b73150609181330r2b86428cq6fb244a3141392f9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/18/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Merlin Moncure" <mmoncure(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2006-09-18 20:44:55 Re: 8.2 beta blockers
Previous Message Neil Conway 2006-09-18 20:28:06 Re: An Idea for OID conflicts