Re: pg on Debian servers

From: Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>
To: pgsql-general(at)PostgreSQL(dot)org
Subject: Re: pg on Debian servers
Date: 2017-11-11 17:29:27
Message-ID: ou7c1o$d2a$1@pye-srv-01.telemetry.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/11/17 16:45, Jan Claeys wrote:
> On Sat, 2017-11-11 at 14:23 +0000, Mark Morgan Lloyd wrote:
>> I think that the "preventing upgrades" route is the one to follow,
>> since inhibiting the restart would obviously present a risk that
>> something loaded dynamically could get out of step. As an at least
>> temporary hack I've disabled unattended updates using
>>
>> # systemctl disable unattended-upgrades.service
>
> Unattended-upgrades is configurable and allows whitelisting package
> origins, as well as blacklisting packages so that they never get
> upgraded automatically (you can still upgrade them manually, of
> course).
>
> See /etc/apt/apt.conf.d/50unattended-upgrades (the default version of
> that file includes documentation as comments).
>
> Also see the unattended-upgrade(8) manpage, and the on/off switch in
> /etc/apt/apt.conf.d/20auto-upgrades

Thanks Jan, noted. I was, of course, working to a fairly traditional
priority: get things running again, whine for a few hours, and only
later implement a proper fix :-)

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christoph Berg 2017-11-11 20:53:16 Re: Postgres 10.1 fails to start: server did not start in time
Previous Message Adam Brusselback 2017-11-11 16:49:30 Re: Postgres 10.1 fails to start: server did not start in time