Re: pg_locks view and user locks

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Subject: Re: pg_locks view and user locks
Date: 2004-09-13 21:04:03
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A74AB@Herge.rcsinc.local
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I said some time ago that I would pester contrib authors about fixing
> license issues, but it still hasn't gotten to the top of my to-do list
:-(
> AFAIK nothing at all has been done on this score.
>
> If Merlin is hot about contrib/userlock right now, he's welcome to try
> to contact the original author and get this dealt with.
>
> The point about not importing documentation from a mislicensed contrib
> module is valid IMHO.

I'll try to contact the author and see what comes up. Supposing the
userlock module is re-licensed (or a suitable replacement is contributed
and accepted), is there any merit to:

Promoting the user lock wrappers out of contrib (plus fleshing them out
a bit)?
Adjusting the pg_locks view to return the user lock specific information
(or, as Alvaro suggested, to add a new view)?
A general documentation update wrt user locks?

Merlin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-09-13 21:25:42 Re: pg_locks view and user locks
Previous Message Tom Lane 2004-09-13 20:39:49 Re: pg_locks view and user locks