From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | 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-23 23:01:16 |
Message-ID: | 3705826352029646A3E91C53F7189E3201674E@sectorbase2.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > For example, one could use user-locks for processing incoming
> > orders by multiple operators:
> > select * from orders where user_lock(orders.oid) = 1 LIMIT 1
> > - so each operator would lock one order for processing and
> > operators wouldn't block each other. So, could such
> > application be commercial with current licence of
> > user_lock()? (Sorry, I'm not licence guru.)
>
> I assume any code that uses contrib/userlock has to be GPL'ed,
> meaning it can be used for commercial purposes but can't be sold
> as binary-only, and actually can't be sold for much because you
> have to make the code available for near-zero cost.
I'm talking not about solding contrib/userlock separately, but
about ability to sold applications which use contrib/userlock.
Sorry, if it was not clear.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-08-23 23:04:28 | Re: User locks code |
Previous Message | Bruce Momjian | 2001-08-23 22:55:24 | Re: User locks code |