RE: Open source licenses

Dear All,

As I solution, I wanted to start to build Postgres from source by myself, in order to better managed what it is finally included.
So I wanted to compile on Windows with Visual Studio.

However, in the page https://www.postgresql.org/docs/current/install-windows.html, I can see:
" It is recommended that most users download the binary distribution for Windows, available as a graphical installer package from the PostgreSQL website. Building from source is only intended for people developing PostgreSQL or extensions. "

Why this recommendation ? Is there any "risk" by building from source ?

Best regards,

Nicolas DAVID
WORKNC DENTAL Project Manager
Manufacturing Intelligence division
Hexagon
E: nicolas(dot)david(at)hexagon(dot)com
HexagonMI.com

CONFIDENTIALITY NOTICE: This email and any attachments may be confidential and protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the e-mail or any attachment is prohibited. If you have received this email in error, please notify us immediately by replying to the sender and deleting this copy and the reply from your system. Thank you for your cooperation. Please note all the views and opinions published here are solely based on the author's own opinion and should not be considered necessarily as reflecting the opinion of Hexagon Manufacturing Intelligence.

-----Original Message-----
From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Sent: 07 April 2021 10:51
To: DAVID Nicolas <nicolas(dot)david(at)hexagon(dot)com>; Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>; pgsql-general(at)postgresql(dot)org
Subject: Re: Open source licenses

This email is not from Hexagon's Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email.

On Wed, 2021-04-07 at 06:41 +0000, DAVID Nicolas wrote:
> > > It is to make an inventory of all the used opensource licenses
> > > from all the used components, to check and respect the terms of use, to preserve copyrights and intellectual property.
> > >
> > > However, when I get PostgreSql binaries for Windows (Zip archive
> > > linked to [EDB]), I can see in installation-notes.html :
> > > -> "The software bundled together in this package is released
> > > under a number of different Open Source licences. By using any
> > > component of this installation package, you agree to abide by the terms and conditions of it's licence."
> > >
> > > Could the PostgreSQL Global Development Group consider to provide these information ?
> >
> > These installation packages are provided by EnterpriseDB, not by the PGDG.
> >
> > I think your request is reasonable, but you'll have to ask the packager.
>
> Yes sure. I also did it ... without answer.

Not nice.

> But my initial question concerned only the open source components
> linked to the PostgreSQL server that are not under the PostgreSQL license( ex: openssl, libcharset, ...).
> Regarding the other modules added by EDB, I will ask again to EDB.

That depends on how PostgreSQL was configured.

It may be a bit cumbersome, but you could go through all the shared libraries
(DLLs) in the "bin" directory that do not belong to PostgreSQL. The licenses for software like OpenSSL should be easy to find.

Yours,
Laurenz Albe
--
Cybertec | https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cybertec-postgresql.com%2F&amp;data=04%7C01%7C%7Cbee5be9a5edc434dabf008d8f9a23e5b%7C1b16ab3eb8f64fe39f3e2db7fe549f6a%7C0%7C0%7C637533822516425483%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=%2FhPlqUOT%2FIciMfm1bNBfIiBDi%2FHoh2qOi8PfApQHPBs%3D&amp;reserved=0