Re: PostrgreSQL Commercial restrictions? - Mailing list pgsql-general

From Richard Broersma
Subject Re: PostrgreSQL Commercial restrictions?
Date
Msg-id CABvLTWHTnkEyTgr0OTAPLidSNh4XEdNyFvK1aeO-nJkZ8qFO-A@mail.gmail.com
Whole thread Raw
In response to Re: PostrgreSQL Commercial restrictions?  (David Johnston <polobo@yahoo.com>)
Responses Re: PostrgreSQL Commercial restrictions?  (Stephen Frost <sfrost@snowman.net>)
List pgsql-general
On Wed, Aug 7, 2013 at 8:43 AM, David Johnston <polobo@yahoo.com> wrote:
Where the PostgreSQL license comes into play is if you make alterations to
the PostgreSQL database itself - the underlying engine implemented in C and
to some degree the supporting utilities written in various languages.
Anything contributed to the core PostgreSQL project becomes open-source but
you are permitted to create a commercial port of PostgreSQL with proprietary
code under terms different from those for the core PostgreSQL project.  As
your application is most likely NOT one of these ports I'll stop here.

That my be true for MySQL, but I don't think the applies to PostgreSQL.  Several companies have forked PostgreSQL into their own proprietary product.

Here's a nice presentation on the subject that was put together by Josh Berkus:
http://www.slideshare.net/pgconf/elephant-roads-a-tour-of-postgres-forks



--
Regards,
Richard Broersma Jr.

pgsql-general by date:

Previous
From: Steve Crawford
Date:
Subject: Re: Staging Database
Next
From: Adrian Klaver
Date:
Subject: Re: How to prevent clear screen when query finish ?