| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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 14:36:53 |
| Message-ID: | 24038.1446475013@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shulgin, Oleksandr | 2015-11-02 14:41:11 | Re: pglogical_output - a general purpose logical decoding output plugin |
| Previous Message | Craig Ringer | 2015-11-02 14:36:07 | Re: pglogical_output - a general purpose logical decoding output plugin |