Re: advisory locks and permissions

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Stephen Frost" <sfrost(at)snowman(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Subject: Re: advisory locks and permissions
Date: 2006-09-22 20:25:29
Message-ID: b42b73150609221325x1cf787adkfcff309bb7490bed@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/22/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I don't see the column rename as an
> > API change issue.
>
> How can you possibly claim it's not an API change?
>

i dunno, i agree with bruce here. we are just changing the output of
pg_locks a bit reflecting the change in moving contrib to core.
nobody cares about the literal output of pg_locks for userlocks except
the old contrib users. compatiblity could be supplied in the pgfoundry
module for this as well. i say to leave the lock tables alone and
change to 'advsiory'. it just seems odd the way it is.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-09-22 20:36:21 Re: advisory locks and permissions
Previous Message Andrew - Supernews 2006-09-22 20:10:09 Re: Fwd: Is the fsync() fake on FreeBSD6.1?