From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_locks view and user locks |
Date: | 2004-09-13 19:36:19 |
Message-ID: | 200409132136.20025.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
Merlin Moncure wrote:
> Second,
> Is there a reason why user level locks are completely undocumented?
> AFAICT, There is no mention of them in anywhere in the docs,
> particularly 12.4, which describes methods for application managed
> concurrency. The availability of cooperative long term locks is
> (IMO) a really nice feature, particularly for people porting legacy
> applications which depend on explicit locking (there is some good
> info in the user lock module which is unfortunately under the GPL).
That's the whole problem. I don't think anyone objects to the user lock
principle, but as long as it's GPL, we won't support it. It was
probably a mistake to accept this module in the first place. I believe
some people have been trying to get the module relicensed, but that
evidently never happened.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-09-13 20:02:25 | Re: [HACKERS] pg_locks view and user locks |
Previous Message | Merlin Moncure | 2004-09-13 17:34:05 | pg_locks view and user locks |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-09-13 20:02:25 | Re: [HACKERS] pg_locks view and user locks |
Previous Message | Merlin Moncure | 2004-09-13 17:34:05 | pg_locks view and user locks |