Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFk1g-00FZNo-1P for pgsql-general@arkaria.postgresql.org; Tue, 26 Nov 2024 01:06:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tFk1e-002MxY-GF for pgsql-general@arkaria.postgresql.org; Tue, 26 Nov 2024 01:05:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFk1e-002MxQ-4q for pgsql-general@lists.postgresql.org; Tue, 26 Nov 2024 01:05:58 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFk1c-003rMC-52 for pgsql-general@postgresql.org; Tue, 26 Nov 2024 01:05:57 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3ea467fda32so833279b6e.1 for ; Mon, 25 Nov 2024 17:05:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732583154; x=1733187954; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=NtuhQBJ4O1xQ2kjFo2FWAbTf156pmllMQuHNQAJ7Tdg=; b=UrQfiMzIPQgCJ4j9gHJojfTOAl+VK90Kb4O0Z6GhEnIo4qGQP2e6LmmEp69dIwUoce UlEFKjKekLq9L0VjtgsdPipKNq3oCPgc2UVJYTNcguF+cWeUk7FfvPJ2tzoJavuEJMpK Yov8UPHdVKzbkUMZNyZrw3Y+MrAIkD/x2rDkFVAaYrQMXZlibuprliEI2+ytOSF5qvtz wugggHTmjLW5+yXu+II42zhMVrOMUgwTpE6sPJ3+9k1VKiQ+0CTmLebMeAyiVVBuEDcK 6QYdLCdA1/k3qxIob8O6KEoUSp6ZzKpXMuFy9KgS4LrSCA9aUbeANoTLbJwDQewFvGoj sPFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732583154; x=1733187954; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NtuhQBJ4O1xQ2kjFo2FWAbTf156pmllMQuHNQAJ7Tdg=; b=Eh02khUqBb5vstBQsgDroMSo3Zp0cKm+qttEG81dNVAfUEzLBjqf82cYqQZOHKBYf7 3lCqZZOtNz+ZNvJv2jYCataedVPs5wfI4VpvNshroZYdTUG2TY8nP9GVHeEjXZMqBonf asPS4qbJHoJhqeA4/R7yO4Xa2xehjlAtvqyiPJOTgbOh2pjeW1GCr111KLChMcUlHxTX /wGs8Sb3kVCVjNB9jyGuuwe27PL37Rnxvh+ULEULBjmSB4FfC4xs2QPkRV5dc87U+Hgr pZSzYZ8Y1EwadMc4dZhSRpc7Z5cm+luQT/K9k+Enm8SsByxvDxVCwZVgXus/cS7ou70i jyIQ== X-Gm-Message-State: AOJu0YzHK6Cs06k4k16JLf/wjcDNf0381SFDyETVOV+h70rNaIWXamwx lTtu0s4UCyJm6KKTJBIul02qCS2PWBAjjvdxA5Nv/rB8YKr4i2EsM1JdOb/9B0sE7vBv0JYbegz 14ILG5ymNBLQGvgfzNDEc1A05i9mTK19t X-Gm-Gg: ASbGnctsSqxeJTzyM7frjdK2GePa+Yb6ScQzf3eDNwp7b3GmjL/c2xLDd+OmiaIRwW7 7Sz8wBfBepl/3+4qxc8klo+MXnUO52ZvI X-Google-Smtp-Source: AGHT+IFOYPLUEpbID/decw/AWKEF0E0gsAg5NUHQsb8paFFc2wXqkfDANww28KQ+5J579Btl/sfb8T3MT/5tePZ936E= X-Received: by 2002:a05:6808:130e:b0:3ea:41b7:de25 with SMTP id 5614622812f47-3ea41b7e342mr6394201b6e.40.1732583153979; Mon, 25 Nov 2024 17:05:53 -0800 (PST) MIME-Version: 1.0 References: <952719356.812136.1732254050572.ref@mail.yahoo.com> <952719356.812136.1732254050572@mail.yahoo.com> <6CF9A64A-5851-4805-BAC5-4EBBACF1E689@thebuild.com> In-Reply-To: From: Ron Johnson Date: Mon, 25 Nov 2024 20:05:43 -0500 Message-ID: Subject: Re: License question To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006fd7f40627c67352" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006fd7f40627c67352 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 25, 2024 at 5:47=E2=80=AFPM Clay Jackson (cjackson) < Clay.Jackson@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). --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000006fd7f40627c67352 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 25, 2024 at 5:47=E2=80=AFPM C= lay Jackson (cjackson) <Clay.J= ackson@quest.com> wrote:
[snip]= =C2=A0
Are you willi= ng to sign up for "maintaining" PostgreSQL in your environment, I= NCLUDING things like patching, finding and fixing bugs, upgrades, backup an= d recovery, and off-hours support?

Azure= 9;s Postgresql managed database handles all that (except off-hours support)= for you, and there's much less off-hours support required (at least th= ere was with AWS RDS Postgresql, so pressuming so with Azure, too).

Of course, OP just mentioned an Azure VM, so he'd hav= e to do all that himself.

Using the Azure Postgres= ql managed database still means you'll have to think about archiving da= ta, and properly configuring PG (mainly autovacuum parameters).
= =C2=A0
--
Death to <Redact= ed>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--0000000000006fd7f40627c67352--