Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iAecU-0004ah-EO for pgsql-general@arkaria.postgresql.org; Wed, 18 Sep 2019 18:24:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iAecT-0003qM-7z for pgsql-general@arkaria.postgresql.org; Wed, 18 Sep 2019 18:24:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iAecS-0003qB-RN for pgsql-general@lists.postgresql.org; Wed, 18 Sep 2019 18:24:00 +0000 Received: from mail-pl1-x642.google.com ([2607:f8b0:4864:20::642]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iAecP-00060h-Hz for pgsql-general@lists.postgresql.org; Wed, 18 Sep 2019 18:23:59 +0000 Received: by mail-pl1-x642.google.com with SMTP id d3so364377plr.1 for ; Wed, 18 Sep 2019 11:23:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NE4gH/R4lpT9wDX6QXsvUwh9lF0EkwBI4Z+AvUcBxy4=; b=pqp6CJWGVvyqIvpBkyWWi36i/NiXVy6OTrlTWrkVEoyrdwfVMzB/JY22j4zO4NOVX5 TITkjfQ8aLKn5KvVkbq50GfKZTCfYMEduZQJi1nWpn2gMgybS7ovlnDI4QvZsd+XG4KR 14cCQvtt6Clxokl3Q7DE1lxWkZeSmRnfkBBFxRoLkSBLmN/tetXLD1Y1s37QMkLItNm3 Pt34FoCLplj4Af6u2TaxxdxMkstKyP4O6bhmV4Wr5SwMI1d0MjOCX4c1jFQvrHGbEBcG 7FnJyUPCmIR1eNdv2y42jk+5ntQNFOK7FUJVno50t3Z25Ixwr6CrBOKehKDvIqQ/y8yd Rhvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NE4gH/R4lpT9wDX6QXsvUwh9lF0EkwBI4Z+AvUcBxy4=; b=WOf6QTaI/TRP75csLXThrBehhJHpuKL6PNKuQ15DvhvwgoY+LS772N7sNZ13w/Ebws Nr0vWIuKS1ZiOSNbSweE2ziE8aBddOdkHqauofhAQ0VURNPOMtNuDZKtNpUayiwm+T75 sPXECYQeTfmSFVD9LsCaHaQ6QMj+j2qmS8ITxKsg41eEwZfFz2Jyu8cEHjeHwymoeGrj kCs/I5Ysm/nSaPueCSzzlmey8A6al6AGxALuQYQ8JOrr8CgNTnaVnDQEhPt3q1grAkRy g4Ov9CDhqUmWETy6c3D6AEuntEGpZGb/0Nu2sIHBPEZQZb9p0t3/L2SKdOIRjHMGcZLR 0fPg== X-Gm-Message-State: APjAAAUwxD6OpBvPjHd4e1SWqgnB+Hm3/iTLF3163Fppl7U/EUhn35dQ hSDHjr/fy0DvPKauUnvB0ac= X-Google-Smtp-Source: APXvYqwoO76cQJ2dHvvu4v9ykZbU57un3YOroWfSYzco9YOvwoYNQGMGq5tU/9m0GsuEgZSr7f/ocg== X-Received: by 2002:a17:902:b08f:: with SMTP id p15mr5759005plr.158.1568831034134; Wed, 18 Sep 2019 11:23:54 -0700 (PDT) Received: from [10.106.130.105] ([155.100.47.1]) by smtp.gmail.com with ESMTPSA id f18sm80822pgf.58.2019.09.18.11.23.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Sep 2019 11:23:53 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: PostgreSQL License From: Rob Sargent In-Reply-To: <11b26b3d-93d5-ac6b-7c06-aa959d91be5d@aklaver.com> Date: Wed, 18 Sep 2019 12:23:51 -0600 Cc: Ashkar Dev , Laurenz Albe , "pgsql-generallists.postgresql.org" , user.postgresql@gmail.com, vikasmanya1@gmail.com, andreas@visena.com, hjp-pgsql@hjp.at Content-Transfer-Encoding: quoted-printable Message-Id: <96C4950E-4157-4BD6-BE04-B4EBEF8F98A4@gmail.com> References: <11b26b3d-93d5-ac6b-7c06-aa959d91be5d@aklaver.com> To: Adrian Klaver X-Mailer: Apple Mail (2.3445.104.11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Sep 18, 2019, at 12:17 PM, Adrian Klaver = wrote: >=20 > On 9/18/19 11:06 AM, Rob Sargent wrote: >> On 9/18/19 11:50 AM, Ashkar Dev wrote: >>> Hi all thanks, >>> I meant maybe I create a web app with PostgreSQL that work locally = for example for a pharmacy that stores data by barcode while the DB was = created by PostgreSQL how I can sell the Database for him, how to = deliver the product to him can I sell the package that contains web app = files with PostgreSQL software and the database code? >>>=20 >> You can charge the pharmacist for your efforts: your web app = (license), installing postgres and your schema (somewhere) and the data = supporting your web-app, any documentation of your web-app and schema, = any maintenance and support you care to specify. You can copy-right your = app and schema and data. >> You cannot (legitimately) charge the pharmacist for any part = PostgresQL. >=20 > Why not? >=20 > Pretty sure that is what third parties are doing with their forks of = Postgres. >=20 I see your point, but aren=E2=80=99t they in essence charging for their = efforts in making, managing their fork. There are plenty of vendors, = for a time I was one, who happily apply a schema to which ever database = the client supplied (mssql, ora, pg in my case).