It is necessary to clarify the situation with the license of the PostgreSQL product downloaded from this page http://www.enterprisedb.com/products-services-training/pgdownload

I have a few questions:

  1. Is it possible, without violating the license, to deliver the PostgreSQL distribution kit on the same optical drive together with the distribution kit of a commercial product developed using the PostgreSQL server?
  2. Is it allowed to run the PostgreSQL installer through a .bat file that passes parameters to the installer without violating the license?
  3. If on the first question the answer is positive, then how should I properly issue a copyright, readme?

I would be very grateful for the detailed answers, indicating the places in the license agreement (sorry, but in English is not strong and not a lawyer, and the situation requires a clear answer without a free translation)

    1 answer 1

    From the FAQ :

    Q: How is PostgreSQL licensed? How much does it cost?
    A: PostgreSQL is released under the OSI-approved PostgreSQL License. There is no fee, even for use in commercial software products. Please see the PostgreSQL License

    Q: What is the PostgreSQL license? How much does it cost?
    A: PostgreSQL is released under an OSI approved PostgreSQL license. It is free, even for use in commercial products. See the PostgreSQL license .

    The PostgreSQL license (see link above) is very short and, in general, allows everything (using, copying, modifying, distributing software and documentation) "for nothing", even without explicit written permission. Only if the text of the license with copyright will be in all copies. That's all the conditions.

    The installer from EnterpriseDB does not demonstrate any license agreement itself, and I do not observe the conditions of use of the installer. But even if it is, it can be a license only for the installer, but not for the postgres.

    • one
      @Fasta and where did you find at least some mention of the obligation to provide the source? A PostgreSQL license does not require this. This is not for you GPL :) Installer EnterpriseDB does not provide them either. - D-side
    • one
      @Fasta since you didn’t change them at all (so that the obligation to publish the source code of the modified version is applied to you), you need to indicate the fact of using the products under the GPL, give the GPL itself and describe the method of obtaining the source codes of these libraries. In postgres it should be done already. - D-side
    • one
      @Fasta You need to understand that I am not a lawyer and I cannot know about the existence of loopholes in the licenses themselves, so if you want to know for sure, consult a lawyer. I argue from what I saw myself. The PostgreSQL license does not impose any restrictions on you other than the need to supply the text of the license along with each copy of the software product. But PostgreSQL itself contains third-party software under other licenses with its own requirements. These requirements must be met by the installer EnterpriseDB, and it complies with them. Additional restrictions for commercial projects GPL, AFAIK, does not contain. - D-side
    • one
      The most “scary” / “draconian” requirement of the GPL is that in cases when the software under the GPL is distributed to the general public, publish the source code of all changes that have been made to this software, roughly so that the software remains “common”. Since you didn’t make any changes, you don’t need to publish anything. - D-side
    • one
      @Fasta Material for additional study: GPL Violations . - D-side