Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kfUtI-0001US-59 for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 18 Nov 2020 21:21:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kfUtH-00016v-4L for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 18 Nov 2020 21:21:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kfUtG-00016k-Qx for pgsql-pkg-debian@lists.postgresql.org; Wed, 18 Nov 2020 21:21:22 +0000 Received: from mail-qk1-x742.google.com ([2607:f8b0:4864:20::742]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kfUt9-0004ti-Kj for pgsql-pkg-debian@lists.postgresql.org; Wed, 18 Nov 2020 21:21:21 +0000 Received: by mail-qk1-x742.google.com with SMTP id q22so3360595qkq.6 for ; Wed, 18 Nov 2020 13:21:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seiler-us.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Tpo0RfFvxC7Ub93vSfrulDwsZOrC3YkZYoPOXYTKVAE=; b=EdyELqwDRASngaDnO14PCqGhijBR84dL1F6xlfTGflPHsA7QleQlTl1M/lOi78GhTO 64FZOnUiDiliFLTcZRdOJlRBij15ujbCFcACa1AhZLjHB9H1fADoADQI74MTt1DL0UsL SsF/fTIikUzfGjMPmf6W0ZpU/a3Fa3YPiQC1zm2d8PyV15isC/8EvmclzmlsYnJkZIRS 3ENumf/da/3FrfzO6HcZ57s8SIO+4RDn5NSiNBKu16RIGhSdqSxg1r3BTioIDiKHoaTV pWJ3VHSaPbdjbjZ0rkoBYv6gh9zfBOqGM1pWyNMQn034BODGSDvcXE1Gtv/c1aYx+277 CWSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Tpo0RfFvxC7Ub93vSfrulDwsZOrC3YkZYoPOXYTKVAE=; b=ZIQwtnvOVCvvWPYaRMsGD9Dc7I82w41vOMUrlds7BjZZUPO4eaXnz0aPzCjoxccTPh SN1+/BjfYYhIkmyDygFXxvIi/M37SqNqpCldq7GXIrwu6VASYYic4ZjNipG/n1BxZvzf u7LWlIk3vttXQifoow+etjiCSl1Qk5lnSExaLJvj/Edq0U4wiCQxBZZ5uQ9zmxMdhw0o 8uywFrY8ydpUiyszHi/y3DVpzs9LNK+LNs1LGfpxJU8P/Xd6WNaXJOVzIPRCsjqz6TEL EsORE5mYWOTfUMfrmiKjZ1kV2zqLfRxQYqacik4X0Q2smp5nywDV2twdk0lBlIjQOUKs /tdQ== X-Gm-Message-State: AOAM530vzJZteT48vbhzhKaENEJhiOgzisTD4jsVQZiROs9+UnlnVIDq GK9QsfQvtPeAm4TXC7MH2/KZAv6duHmVgvzHVS2/sA== X-Google-Smtp-Source: ABdhPJzLGZdPEuN6we+DIinMm1kc8N+czKrLC+OK5YVeX4wvI4uGaLw7POlhYJRmkESECY5Bl70NizKnAqQ3z41EEmU= X-Received: by 2002:a37:a783:: with SMTP id q125mr7147833qke.10.1605734474404; Wed, 18 Nov 2020 13:21:14 -0800 (PST) MIME-Version: 1.0 References: <20201118211206.GA412486@msg.df7cb.de> In-Reply-To: <20201118211206.GA412486@msg.df7cb.de> From: Don Seiler Date: Wed, 18 Nov 2020 15:21:03 -0600 Message-ID: Subject: Re: Ubuntu Unattended Upgrades To: Christoph Berg Cc: pgsql-pkg-debian@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000f36f1905b46830e5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000f36f1905b46830e5 Content-Type: text/plain; charset="UTF-8" On Wed, Nov 18, 2020 at 3:12 PM Christoph Berg wrote: > Re: Don Seiler > > 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. > > Hmm, I wasn't aware that Ubuntu's (?) default unattended-upgrades > config makes it upgrade Ubuntu packages only. > By default it only upgrades from an approved list of sources. One could include PGDG repos in that list if you desired. > > 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 > > You can install a /usr/sbin/policy-rc.d file [1]. That will allow > filtering the start/stop actions issued by package activity. > > [1] https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt I'll look into this, thanks! > > > > 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). > > Restarting after install is actually the default since a while ago. > (Previously packages were doing stop-upgrade-start.) > Right but I mean restarting like later in the day or week. Not immediately after the upgrade when we aren't ready for it. Thanks for all the info! Don. -- Don Seiler www.seiler.us --000000000000f36f1905b46830e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 18, 2020 at 3:12 PM Christoph= Berg <myon@debian.org> wrote:=
Re: Don Seiler
> 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 the= n also restarts
> the databases. It seems this is only a problem with postgresql-10 on U= buntu
> Bionic since Bionic provides its own postgresql-10 packages.

Hmm, I wasn't aware that Ubuntu's (?) default unattended-upgrades config makes it upgrade Ubuntu packages only.

By default it only upgrades from an approved list of sources. One co= uld include PGDG repos in that list if you desired.
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex"> > Alternatively, is it possible to install the new packages but *NOT* re= start
> the DB automatically? I understand that a DB restart would be required= to

You can install a /usr/sbin/policy-rc.d file [1]. That will allow
filtering the start/stop actions issued by package activity.

[1] https://people.debian.org/= ~hmh/invokerc.d-policyrc.d-specification.txt

I'll look into this, thanks!
=C2=A0


> run on the new version but curious if we could have the packages insta= lled
> prior and then restart at the next available window (although installa= tion
> doesn't really take that long, just curious).

Restarting after install is actually the default since a while ago.
(Previously packages were doing stop-upgrade-start.)
<= br>
Right but I mean restarting like later in the day or week. No= t immediately after the upgrade when we aren't ready for it.
=
Thanks for all the info!

Don.=C2=A0=


--
Don Seiler
www.seiler.us
--000000000000f36f1905b46830e5--