public inbox for [email protected]
help / color / mirror / Atom feedFrom: Clay Jackson (cjackson) <[email protected]>
To: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: RE: License question
Date: Tue, 26 Nov 2024 01:20:22 +0000
Message-ID: <CO1PR19MB498416605559A6D264044A899B2F2@CO1PR19MB4984.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CANzqJaALqDXFOi7pJDcB6wYbK1x68OtgA=U7zff_Uahrjik+bA@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CO1PR19MB49843F419EA427C1D1B45BA69B2E2@CO1PR19MB4984.namprd19.prod.outlook.com>
<CANzqJaALqDXFOi7pJDcB6wYbK1x68OtgA=U7zff_Uahrjik+bA@mail.gmail.com>
Thanks, Ron! Exactly my points!
I do not want to “discount” the community in ANY way. In fact, I’m a huge fan of Open Source, as long as everyone, including “management”, is bought into community support concept.
I’ve seen the “wrong side” of “What do you mean, ‘You posted something to the list’? Why can’t you CALL someone (and/or get someone logged in) RIGHT NOW?” discussions, usually “in the heat of battle”, a few too many times.
Of course, the flip side of this is “Whew – the community solved this before the <large software support organization> even got back to me”.
It comes down to being “fully informed”.
Clay Jackson
Database Solutions Architect
From: Ron Johnson <[email protected]>
Sent: Monday, November 25, 2024 5:06 PM
To: pgsql-general <[email protected]>
Subject: Re: License question
CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
On Mon, Nov 25, 2024 at 5:47 PM Clay Jackson (cjackson) <[email protected]<mailto:[email protected]>> wrote:
[snip]
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?
Azure's Postgresql managed database handles all that (except off-hours support) for you, and there's much less off-hours support required (at least there was with AWS RDS Postgresql, so pressuming so with Azure, too).
Of course, OP just mentioned an Azure VM, so he'd have to do all that himself.
Using the Azure Postgresql managed database still means you'll have to think about archiving data, and properly configuring PG (mainly autovacuum parameters).
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (4+ messages) latest in thread
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]
Subject: RE: License question
In-Reply-To: <CO1PR19MB498416605559A6D264044A899B2F2@CO1PR19MB4984.namprd19.prod.outlook.com>
* 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