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 <ronljohnso...@gmail.com> Sent: Monday, November 25, 2024 5:06 PM To: pgsql-general <pgsql-gene...@postgresql.org> 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) <clay.jack...@quest.com<mailto:clay.jack...@quest.com>> 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!
