Re: PostgreSQL Licensing Question for pg_crypto and tablefunc extensions

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:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=README;h=6416a8cf3b4677c4828f775c402bf18631f35b00;hb=HEAD

Which refers to COPYRIGHT:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=COPYRIGHT;h=655a3c59d60f54a824cc8ad6c94a4522f2b465cd;hb=HEAD

>
> Best Regards,
> Rumpi
>
> On Thu, Feb 25, 2021 at 6:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> Rumpi Gravenstein <rgravens(at)gmail(dot)com <mailto:rgravens(at)gmail(dot)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
>
>
>
> --
> Rumpi Gravenstein

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com