From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER SYSTEM vs symlink |
Date: | 2015-11-02 18:27:33 |
Message-ID: | 5637AB15.6030801@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/02/2015 06:36 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> I don't know if this was discussed at the time ALTER SYSTEM was
>> implemented, but I have just discovered that if postgresql.auto.conf is
>> a symlink to a file elsewhere, ALTER SYSTEM will happily break that link
>> and write its own local copy. That strikes me as rather unfriendly. Why
>> not just truncate the file rather than unlink it as it's being
>> rewritten? Even if we don't want to do that a warning in the docs might
>> help users avoid the "mistake" I just made.
>
> Frankly, that behavior strikes me as a good idea. There is no situation,
> IMV, where it's sane to try to put a symlink there.
So, just a doc patch then?
Since we have both include files and config_dir, I really don't
understand why anyone symlinks conf files anymore. Anyone care to
enlighten me?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2015-11-02 18:35:15 | Re: fortnight interval support |
Previous Message | Robert Haas | 2015-11-02 18:10:38 | Re: remove wal_level archive |