Re: advisory locks and permissions - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: advisory locks and permissions
Date
Msg-id b42b73150609221325x1cf787adkfcff309bb7490bed@mail.gmail.com
Whole thread Raw
In response to Re: advisory locks and permissions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: advisory locks and permissions
List pgsql-hackers
On 9/22/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bruce Momjian <bruce@momjian.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


pgsql-hackers by date:

Previous
From: Andrew - Supernews
Date:
Subject: Re: Fwd: Is the fsync() fake on FreeBSD6.1?
Next
From: Bruce Momjian
Date:
Subject: Re: advisory locks and permissions