public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Clay Jackson (cjackson) <[email protected]>
To: Christophe Pettus <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: License question
Date: Mon, 25 Nov 2024 15:52:04 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CO1PR19MB49843F419EA427C1D1B45BA69B2E2@CO1PR19MB4984.namprd19.prod.outlook.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CO1PR19MB49843F419EA427C1D1B45BA69B2E2@CO1PR19MB4984.namprd19.prod.outlook.com>
On 11/25/24 14:47, Clay Jackson (cjackson) wrote:
> Christophe is spot on when it comes to the PostgreSQL software.
>
> Not trying to be "snarky" or condescending, but there are some other considerations. "Open Source" or "Free" does not mean "without cost".
>
> No matter where you decide to host the software, there will be storage, compute, and network costs, not only to support the software itself, but also the data you store.
>
> With respect to the data, since you or your employer have decided to persistently store the data in a database, I would presume the data, and more importantly, access to that data, has value.
>
> It seems from the original post that you've decided to pay someone (a cloud vendor) to "take care" of the storage, network, and compute "services". That's great!
>
> But, what about that "non-licensed" software? Once you use that software to store and access your data, you have created a CONTINUING need for that software. What will it cost you or your employer if a "bug" in that software prevents access to, or worse yet, corrupts your data.
1) It is not "non-licensed", it is permissively licensed.
2) Not sure what the point of '... CONTINUING need for that software'
is? If you have a process that depends on something to run then you have
established a need. If you don't want that then don't start any project.
>
> Are you willing to sign up for "maintaining" PostgreSQL in your environment, INCLUDING things like patching, finding and fixing bugs, upgrades, backup and recovery, and off-hours support? If you or your employer have any concerns about this, and IHMO, you should, you might want to consider a "licensed and supported" version of PostgreSQL. There are several out there, including EDB and others. Even the big cloud vendors have "support plans" for PostgreSQL.
That is done by the community as shown here:
https://www.postgresql.org/developer/
and here:
https://www.postgresql.org/support/
and here:
https://www.postgresql.org/support/versioning/
and here:
https://www.postgresql.org/docs/current/backup.html
As to off hours support look at the timestamps here:
https://www.postgresql.org/list/pgsql-general/
Now if you want a specific company to contact then yes there is this:
https://www.postgresql.org/support/professional_support/
https://www.postgresql.org/support/professional_hosting/
>
> Oh, and don't forget, a backup only as good as the last time you tested a restore.
>
> Clay Jackson
> Database Solutions Architect
> [email protected]
>
> -----Original Message-----
> From: Christophe Pettus <[email protected]>
> Sent: Monday, November 25, 2024 11:59 AM
> To: prashant sinha <[email protected]>
> Cc: [email protected]
> Subject: Re: License question
>
--
Adrian Klaver
[email protected]
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: License question
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox