Re: User locks code

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: User locks code
Date: 2001-08-24 00:31:56
Message-ID: 200108240031.f7O0VuM02195@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I definitely agree with Vadim here: it's fairly silly that the
> contrib userlock code is GPL'd, when it consists only of a few dozen
> lines of wrapper for the real functionality that's in the main backend.
> The only thing this licensing setup can accomplish is to discourage
> people from using the userlock code; what's the value of that?
>
> Besides, anyone who actually wanted to use the userlock code would need
> only to write their own wrapper functions to get around the GPL license.

Hey, I agree with Vadim too. The GPL license is just a roadblock, but I
can't tell Massimo what to do with his code if it is not in the backend
proper.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amandeep Singh 2001-08-24 00:33:14 ERP Applications on Postgresql -- ERPTool
Previous Message Hiroshi Inoue 2001-08-24 00:22:57 Re: CURRENT OF cursor without OIDs