PostgreSQL, LGPL and GPL.

From: "Karen Hill" <karen_hill22(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: PostgreSQL, LGPL and GPL.
Date: 2006-10-20 18:29:54
Message-ID: 1161368994.197996.40080@k70g2000cwa.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I was looking through the various contrib packages and pgfoundry
projects. I noticed that many of them are GPL like PostGIS or LGPL
like Npgsql. I have questions.

If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your database (tables, stored
procedures, views, etc) are GPL? Like wise if you create a client that
connects to that database, do they also become GPL? Does PostgreSQL in
effect become GPL when using PostGIS because PostGIS accesses parts of
PostgreSQL?

Npgsql is LGPL. It means you must release the source of Npgsql when
distributing it, and if you modify Npgsql, but not have to release the
source under the (L)GPL of the software that calls Npgsql functions?

If you provide the source on a CD and the (GPL/LGPL) license as a text
file on that CD if you distribute, then are your obligations met under
the GPL/LGPL? What if those you distribute to lose the source code CD,
can they then come after you X number of years later demanding the
source?

For the developers of LGPL/GPL like Npgsql, why do you not dual
license? Have a model like MySQL where one can purchase a BSD licensed
version or use the GPL/LGPL one.

regards,
Karen

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Bauer 2006-10-20 18:41:50 Re: Overload after some minutes, please help!
Previous Message Brandon Aiken 2006-10-20 18:24:39 Re: Upgrade 7.4 to 8.1 or 8.2?