From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostrgreSQL Commercial restrictions? |
Date: | 2013-08-07 15:54:05 |
Message-ID: | CABvLTWHTnkEyTgr0OTAPLidSNh4XEdNyFvK1aeO-nJkZ8qFO-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Aug 7, 2013 at 8:43 AM, David Johnston <polobo(at)yahoo(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-08-07 16:01:12 | Re: How to prevent clear screen when query finish ? |
Previous Message | Steve Crawford | 2013-08-07 15:53:23 | Re: Staging Database |