MIME-Version: 1.0
From: Don Seiler <don@seiler.us>
Date: Wed, 18 Nov 2020 10:22:58 -0600
Message-ID: 
 <CAHJZqBBzix3=9dP=kAiLi3Y-YGCJKb=t6F+_L4D+SL7MxX8gtA@mail.gmail.com>
Subject: Ubuntu Unattended Upgrades
To: pgsql-pkg-debian@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000e314ee05b464060f"
Precedence: bulk

--000000000000e314ee05b464060f
Content-Type: text/plain; charset="UTF-8"

Good morning,

Background: Running PG10 on Ubuntu Bionic (18.04).

Last night I noticed one of our prod databases was restarted. Digging
deeper it was Ubuntu's unattended-upgrade utility (which we just started
using this month) that upgraded it from the PGDG 10.14 package to the
Ubuntu 10.15 package.

We had assumed since unattended-upgrade doesn't include PGDG that it
wouldnt upgrade the existing packages, but apparently that doesn't prevent
it from "upgrading" them to the Ubuntu equivalent, which then also restarts
the databases. It seems this is only a problem with postgresql-10 on Ubuntu
Bionic since Bionic provides its own postgresql-10 packages.

I'm guessing we should blacklist all postgresql packages in the
unattended-upgrades config. I'm wondering if this has been already tackled
by anyone else and if there is a more clever solution other than NOT
running unattended-upgrades.

Alternatively, is it possible to install the new packages but *NOT* restart
the DB automatically? I understand that a DB restart would be required to
run on the new version but curious if we could have the packages installed
prior and then restart at the next available window (although installation
doesn't really take that long, just curious).

-- 
Don Seiler
www.seiler.us

--000000000000e314ee05b464060f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Good morning,<div><br></div><div>Background: Running PG10 =
on Ubuntu Bionic (18.04).<br><div><br></div><div>Last night I noticed one o=
f our prod databases was restarted. Digging deeper it was Ubuntu&#39;s unat=
tended-upgrade utility (which we just started using this month) that upgrad=
ed it from the PGDG 10.14 package to the Ubuntu 10.15 package.<br clear=3D"=
all"><div><br></div><div>We had assumed since unattended-upgrade doesn&#39;=
t include PGDG that it wouldnt upgrade the existing packages, but apparentl=
y=C2=A0that doesn&#39;t prevent it from &quot;upgrading&quot; them to the U=
buntu equivalent, which then also restarts the databases. It seems this is =
only a problem with postgresql-10 on Ubuntu Bionic since Bionic provides it=
s own postgresql-10 packages.</div><div><br></div><div>I&#39;m guessing we =
should blacklist all postgresql packages in the unattended-upgrades config.=
 I&#39;m wondering if this has been already tackled by anyone else and if t=
here is a more clever solution other than NOT running unattended-upgrades.<=
br><br>Alternatively, is it possible to install the new packages but *NOT* =
restart the DB automatically? I understand that a DB restart would be requi=
red to run on the new version but curious if we could have the packages ins=
talled prior and then restart at the next available window (although instal=
lation doesn&#39;t really take that long, just curious).</div><div><br></di=
v>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail=
_signature"><div dir=3D"ltr"><div>Don Seiler<br><a href=3D"http://www.seile=
r.us" target=3D"_blank">www.seiler.us</a></div></div></div></div></div></di=
v>

--000000000000e314ee05b464060f--