From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: initdb when data/ folder has mount points |
Date: | 2018-02-22 13:22:04 |
Message-ID: | 3736b74f-1ff8-41b8-675d-7913cef23894@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/22/18 1:16 AM, Michael Paquier wrote:
> On Wed, Feb 21, 2018 at 07:56:38PM -0500, David Steele wrote:
>> On 2/21/18 7:01 PM, Tom Lane wrote:
>>> For pg_log, just put it somewhere else and set the appropriate
>>> configuration option to say where to write the postmaster log files.
>>> Or you could use a symlink, like the solution for pg_xlog, but
>>> I don't see any advantage there.
>>
>> Symlinking pg_log is not ideal because the logs end up in the backup. It
>> gets pretty weird when those logs get restored to a standby and somebody
>> starts reading them.
>
> log_directory in postgresql.conf san be set up with an absolute
> directory value. So there is no actual need for a symlink with pg_log.
> This also reduces the amount of data transfered as part of base
> backups without actually needing them.
Yes, I really should have said having pg_log in the data directory at
all is not ideal, symlinked or no.
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2018-02-22 14:21:04 | Re: initdb when data/ folder has mount points |
Previous Message | Julián Jiménez González | 2018-02-22 12:28:47 | Re: Building PostgreSQL old version from source to test vulnerability CVE-2017-7546 |