Re: User locks code

From: teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 16:02:54
Message-ID: xuy1ym1fntd.fsf@halden.devel.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> > Tom Lane wrote:
> > >
> > > 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.
> >
>
> I was incorrect in something I said to Vadim. I said stored procedures
> would have to be released if linked against a GPL'ed backend.

Only to those you actually distribute this product to. If you're using
it internally, you have no obligations to release it to anyone, to
give one example.

--
Trond Eivind Glomsrød
Red Hat, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-08-24 16:03:34 Re: User locks code
Previous Message Larry Rosenman 2001-08-24 15:33:55 /bin/ld -G vs /usr/ccs/bin/cc -G