Re: pg on Debian servers

From: rob stone <floriparob(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg on Debian servers
Date: 2017-11-12 19:52:49
Message-ID: 1510516369.4986.11.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 2017-11-11 at 14:30 +0100, Magnus Hagander wrote:
>
>
>
> The init.d script is not used with systemd.
>
>
>
Hello Magnus,

Many months ago on a bog standard Debian set-up did a re-boot and ended
up with postmasters running for 9.2, 9.4, 9.5 and 9.6 all started one
after the other. There was a script in init.d which read thru
/usr/lib/postgresql and it started running Postgres for each version it
found. Fortunately, all listening on different ports.

The fix was to disable that script as well as the systemd service.

Doing the upgrade to 10 in a few weeks. Will let you know how it goes.

I assume you are aware of this DSA:-

Debian Security Advisory DSA-4029-1

-----------------------------------------------------------------------

Package : postgresql-common
CVE ID : CVE-2017-8806

It was discovered that the pg_ctlcluster, pg_createcluster and
pg_upgradecluster commands handled symbolic links insecurely which
could result in local denial of service by overwriting arbitrary files.

For the oldstable distribution (jessie), this problem has been fixed
in version 165+deb8u3.

For the stable distribution (stretch), this problem has been fixed in
version 181+deb9u1.

Cheers,
Rob

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2017-11-12 21:03:09 Re: Postgres 10.1 fails to start: server did not start in time
Previous Message Tom Lane 2017-11-12 19:26:42 Re: Postgres 10.1 fails to start: server did not start in time