PostgreSQL Licensing Question for pg_crypto and tablefunc extensions
All,
Postgres 13.1
I am new to PostgreSQL and am unclear on how licensing works for PostgreSQL
extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
community edition or do PostgreSQL extensions fall under a separate
license? I've looked for documentation on this and haven't found anything
on-point. Is there a link that describes how each extension is licensed?
--
Rumpi Gravenstein
Rumpi Gravenstein <rgravens@gmail.com> writes:
I am new to PostgreSQL and am unclear on how licensing works for PostgreSQL
extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
community edition or do PostgreSQL extensions fall under a separate
license? I've looked for documentation on this and haven't found anything
on-point. Is there a link that describes how each extension is licensed?
Everything in contrib/ is considered to be under the same license as the
rest of the distribution. (A few of them have their own copyright text,
but it's not substantially different in meaning from the main copyright
notice. This is also true of bits of the core server, actually.)
Extensions you get from elsewhere might have different copyrights though.
regards, tom lane
Tom
Thanks for the quick reply. What you stated is what I was expecting. I've
searched high and low for the documentation that proves that point --
something I need to do to satisfy our legal team. Any thoughts on under
which rock that license language exists?
Best Regards,
Rumpi
On Thu, Feb 25, 2021 at 6:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Rumpi Gravenstein <rgravens@gmail.com> writes:
I am new to PostgreSQL and am unclear on how licensing works for
PostgreSQL
extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
community edition or do PostgreSQL extensions fall under a separate
license? I've looked for documentation on this and haven't foundanything
on-point. Is there a link that describes how each extension is licensed?
Everything in contrib/ is considered to be under the same license as the
rest of the distribution. (A few of them have their own copyright text,
but it's not substantially different in meaning from the main copyright
notice. This is also true of bits of the core server, actually.)Extensions you get from elsewhere might have different copyrights though.
regards, tom lane
--
Rumpi Gravenstein
On 2/26/21 11:39 AM, Rumpi Gravenstein wrote:
Tom
Thanks for the quick reply. What you stated is what I was expecting.
I've searched high and low for the documentation that proves that point
-- something I need to do to satisfy our legal team. Any thoughts on
under which rock that license language exists?Best Regards,
Rumpi
Hm, make legal prove it isn't FOSS.
On 2/26/21 10:39 AM, Rumpi Gravenstein wrote:
Tom
Thanks for the quick reply. What you stated is what I was expecting.
I've searched high and low for the documentation that proves that point
-- something I need to do to satisfy our legal team. Any thoughts on
under which rock that license language exists?
Try:
README from source:
Which refers to COPYRIGHT:
Best Regards,
RumpiOn Thu, Feb 25, 2021 at 6:26 PM Tom Lane <tgl@sss.pgh.pa.us
<mailto:tgl@sss.pgh.pa.us>> wrote:Rumpi Gravenstein <rgravens@gmail.com <mailto:rgravens@gmail.com>>
writes:I am new to PostgreSQL and am unclear on how licensing works for
PostgreSQL
extensions. Are pg_crypto and tablefunc licensed with the PostgreSQL
community edition or do PostgreSQL extensions fall under a separate
license? I've looked for documentation on this and haven't foundanything
on-point. Is there a link that describes how each extension is
licensed?
Everything in contrib/ is considered to be under the same license as the
rest of the distribution. (A few of them have their own copyright text,
but it's not substantially different in meaning from the main copyright
notice. This is also true of bits of the core server, actually.)Extensions you get from elsewhere might have different copyrights
though.regards, tom lane
--
Rumpi Gravenstein
--
Adrian Klaver
adrian.klaver@aklaver.com
On Fri, Feb 26, 2021 at 12:01 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:
Which refers to COPYRIGHT:
The COPYRIGHT file indeed is serving as the in-repo documentation of our
license. My only gripe is that it fails to explicitly say "The PostgreSQL
License", per [1]https://opensource.org/licenses/postgresql.
As the COPYRIGHT file exists at the top of the repo all source code
underneath, including the contrib directory, is covered.
[1]: https://opensource.org/licenses/postgresql
David J.
David,
Thank you -- that is exactly what I needed!
On Fri, Feb 26, 2021 at 2:06 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:
On Fri, Feb 26, 2021 at 12:01 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:Which refers to COPYRIGHT:
The COPYRIGHT file indeed is serving as the in-repo documentation of our
license. My only gripe is that it fails to explicitly say "The PostgreSQL
License", per [1].As the COPYRIGHT file exists at the top of the repo all source code
underneath, including the contrib directory, is covered.[1] https://opensource.org/licenses/postgresql
David J.
--
Rumpi Gravenstein