pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: License for PostgreSQL for commercial purpose
Date: Thu, 25 Mar 2004 18:04:10 -0500
Message-ID: <603c7wr0k5.fsf@dev6.int.libertyrms.info> (raw)
References: <EAE17A10E81E3D41B0C346D99E83680669E0FE@cklsmail.ck-lifesciences.com>

eric.yum@ck-lifesciences.com ("Eric Yum") writes:
> I am a developer of one commercial organization. We are going to
> develop some applications with PostgreSQL 7.3.3. I learn from some
> websites that it cost no charge for developing software with
> PostgreSQL in commercial environment. However, I saw the PostgreSQL
> is under two type of licenses, namely, X11-style license and BSD
> license for the following websites, :p>
>
> http://www.postgresql.org/licence.html:p;
>
> http://www.gnu.org/directory/database/servers/postgresql.html:p;
>
> Please kindly provide professional comment on this issue and suggest
> whether the use of PostgreSQL for commercial purpose is no license
> charge or not :p>

What you are observing is that the Free Software Foundation (who hold
the gnu.org domain) felt a need to write up their own interpretation
of what they feel various licenses mean.

The FSF characterizes the PostgreSQL license as being "an X11 style
license."  They felt a need to distinguish between different
variations of licenses that are called 'BSD licenses.'

The FSF web site then compares various variations on "BSD licenses,"
considering that there are some that they deem to be "free" (in their
terms), and that there are others that they deem to _NOT_ be "free"
(again in their terms).

None of that establishes that there is actually more than one license
under which you can obtain PostgreSQL; it merely indicates that the
FSF felt the need to use a different name for the license.

There aren't two licenses; there's just one.  And it allows you to use
PostgreSQL for whatever purpose you like without imposing any
licensing fees.

I also find it quite curious that you intend to deploy applications
with a version of PostgreSQL that is known to have bugs fixed by later
releases.  The fact that version 7.3.6 has been released should be
clearly interpreted as indicating that there were problems with all
preceding versions, and that users are to be encouraged to upgrade to
that version.  

Furthermore, 7.4.2 has been released, offering substantial performance
and other functionality advantages over the 7.3 series.  It would seem
odd to start developing applications with a version that has already
been (arguably) superceded by a new major release.
-- 
let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];;
http://cbbrowne.com/info/linux.html
Rules of the Evil Overlord #130.  "All members of my Legions of Terror
will  have professionally  tailored  uniforms. If  the  hero knocks  a
soldier unconscious and steals the uniform, the poor fit will give him
away." <http://www.eviloverlord.com/;



view thread (15+ messages)  latest in thread

Message-ID: <603c7wr0k5.fsf@dev6.int.libertyrms.info>
Permalink:  ../603c7wr0k5.fsf@dev6.int.libertyrms.info/
Also on:    postgresql.org/message-id/603c7wr0k5.fsf@dev6.int.libertyrms.info

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: License for PostgreSQL for commercial purpose
  In-Reply-To: <603c7wr0k5.fsf@dev6.int.libertyrms.info>
  References: <EAE17A10E81E3D41B0C346D99E83680669E0FE@cklsmail.ck-lifesciences.com> <603c7wr0k5.fsf@dev6.int.libertyrms.info>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox