Date: Thu, 17 Sep 2015 14:49:17 +0200
From: Bernd Helmle <mailings@oopsware.de>
To: Jeff Frost <jeff@pgexperts.com>
cc: pgsql-pkg-yum@postgresql.org
Subject: Re: systemd service files vs. postgresql9x-setup 
Message-ID: <6BCC2B177DD8C95F954B4E1D@eje.credativ.lan>
In-Reply-To: <0AC9AAC9-0B01-47E3-860F-620C5F0912F1@pgexperts.com>
References: <0EDD19E44F05669CE0D68F45@eje.credativ.lan>
 <0AC9AAC9-0B01-47E3-860F-620C5F0912F1@pgexperts.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=838
Precedence: bulk
Sender: pgsql-pkg-yum-owner@postgresql.org


--On 12. August 2015 16:54:41 -0700 Jeff Frost <jeff@pgexperts.com> wrote:

>> Opinions?
>>=20
>> [1] <http://www.freedesktop.org/software/systemd/man/systemd.unit.html>
>=20
> Unfortunately, I=E2=80=99m not that familiar with systemd yet and Devrim =
is out
> for a few weeks, so we might not get to this very quickly.

So i'd like to step in again into this patch.

We're working with a RHEL7 environment where those drop-in configurations
are heavily used to move PGDATA to different places and i'd like to
preserve that behavior.

Recap:

postgresql9[45]-setup happily overwrites any PGDATA setting derived from
drop-in configurations by examining the service file directly and ignoring
the previous retrieved setting from systemctl.

So this looks worth to fix for any setups, even when other ways to setup
PGDATA are used.

--=20
Thanks

	Bernd


--=20
Sent via pgsql-pkg-yum mailing list (pgsql-pkg-yum@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-yum