public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Merlin Moncure <[email protected]>
To: [email protected]
Subject: Re: pg_locks view and user locks
Date: Mon, 13 Sep 2004 21:36:19 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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/
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pg_locks view and user locks
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox