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 1qWkqV-004Gj2-Ka for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 17 Aug 2023 21:47:59 +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 1qWkqR-0055nd-ST for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 17 Aug 2023 21:47:56 +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 1qWkqR-0055kT-AQ for pgsql-pkg-debian@lists.postgresql.org; Thu, 17 Aug 2023 21:47:55 +0000 Received: from mail-yb1-xb30.google.com ([2607:f8b0:4864:20::b30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qWkqN-000jsv-8I for pgsql-pkg-debian@lists.postgresql.org; Thu, 17 Aug 2023 21:47:54 +0000 Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-d3d729a08e4so326279276.3 for ; Thu, 17 Aug 2023 14:47:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pavely.net; s=google; t=1692308869; x=1692913669; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=osXd2e35FDHjHQ6kh3tM1FXePGKyOMNBfl0pqeoJB5c=; b=jYlvg/vACsVseJ4cXKy6cg/CVL4ypVuWypu+UnT090JxwhJSR9QPWpZ1uvCaJI51Q3 qIlisXYJc9gKUXXkXEij3jawCj72rPTlM5P+O1mRFnmPFy5v6/d8sT75ZuAzlaFBi1Ac u0aNtRI2DtnNh0jBNfQVt+Q1qSQgjwqMlJ4B8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692308869; x=1692913669; h=cc: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=osXd2e35FDHjHQ6kh3tM1FXePGKyOMNBfl0pqeoJB5c=; b=QmOFxA1cibMvq7bV9Cz6iZcFiC8FOjVVtUfIBAojt+BPTFtmpcFBlLqHOw5SOZt1xk 4oOWTOt8pcKADlFoT3SWIunBOU+CxhuKYiWkMArfbgxkdpYyhicDr9gFecl/KcYa1gqP EIuhClB8BmVVb4BpchnBXYnSOkbsrJzcJ1DcQrePLExJPyPG5vWZY76hNjWfNnCcEZTK DY7HDKzF4lJrzc/cimR18iVt2J4kDJMoc9/27YH2UkRWvUeVv4GTQszqG4H/NsiQWxwf wiIjtOeI0RFaLQM1rFjgK3n4VRGWPeBELjca33cWwFYl2FMvJFFBusfojr0GUHzGt/ej dZEA== X-Gm-Message-State: AOJu0YyrFZlr8t34uiaRVQVH2m2UCWkuree65xLJ8an7N4F/+HvZlwIq ThCZ/AJyGnUZm2WSwY7wtQNaLZG9jNDU/3UVVt9h0Q== X-Google-Smtp-Source: AGHT+IEmxEYdGrj7ACO1LxgAY6u26OCmQlOR/Qta91rHtkhASmNTXySH+4ek91Az2Jeet9hLS5YffmSCNE+eggeROD8= X-Received: by 2002:a25:d1ce:0:b0:d05:3d5b:b63 with SMTP id i197-20020a25d1ce000000b00d053d5b0b63mr961118ybg.25.1692308868989; Thu, 17 Aug 2023 14:47:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aaron Pavely Date: Thu, 17 Aug 2023 16:47:38 -0500 Message-ID: Subject: Re: Ubuntu bionic (18.04) moving to apt-archive.postgresql.org To: Don Seiler Cc: Christoph Berg , PostgreSQL in Debian Content-Type: multipart/alternative; boundary="000000000000fc9dbc0603255c42" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fc9dbc0603255c42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2023 at 4:15=E2=80=AFPM Don Seiler wrote: > On Thu, Aug 17, 2023 at 3:18=E2=80=AFPM Christoph Berg = wrote: > >> Re: Don Seiler >> > > deb https://apt-archive.postgresql.org/pub/repos/apt bionic-pgdg mai= n >> > >> > Would this just be an issue for new installations on bionic? i.e. my >> > current fleet of bionic DB servers would continue to operate, just no >> > updates (which there haven't been any since May anyway)? We're in the >> > middle of our migration to Ubuntu jammy but it'll be a couple months >> yet. >> >> New installations should just work with the above sources line. >> > > Yes, of course. I meant to ask if an existing bionic VM with PG already > installed and running would see any issues if they don't make any > adjustments at all. > This depends. PostgreSQL itself won't mind this one bit, but since the package repository won't exist any longer (i.e., broken), when running 'apt-get update', some processes will take that status as an error in package management. This may break automation if the automation depends on _all_ repositories functioning properly. For instance, you may see this as an issue if adding the host to Canonical's ESM repositories. Chef/Puppet/Ansible/etc. might not like it, either. -- Aaron --000000000000fc9dbc0603255c42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Aug 17, 2023 at 4:15=E2=80=AFPM D= on Seiler <don@seiler.us> wrote:=
On Thu, Aug 17, 2023 at 3:18= =E2=80=AFPM Christoph Berg <myon@debian.org> wrote:
Re: Don Seiler
> > deb https://apt-archive.postgresql.org/pub= /repos/apt bionic-pgdg main
>
> Would this just be an issue for new installations on bionic? i.e. my > current fleet of bionic DB servers would continue to operate, just no<= br> > updates (which there haven't been any since May anyway)? We're= in the
> middle of our migration to Ubuntu jammy but it'll be a couple mont= hs yet.

New installations should just work with the above sources line.

Yes, of course. I meant to ask if an existing bion= ic VM with PG already installed and running would see any issues if they do= n't make any adjustments at all.

This depends. PostgreSQL itself won't mind this one bi= t, but since the package repository won't exist any longer (i.e., broke= n), when running 'apt-get update', some processes will take that st= atus as an error in package management.

This may b= reak automation if the=C2=A0automation depends on _all_ repositories functi= oning properly. For instance, you may see this as an issue if adding the ho= st to Canonical's ESM repositories. Chef/Puppet/Ansible/etc. might not = like it, either.
--
Aaron
=
--000000000000fc9dbc0603255c42--