Re: initdb when data/ folder has mount points

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: initdb when data/ folder has mount points
Date: 2018-02-22 14:21:04
Message-ID: 40496a1d-3b3e-e36e-48fc-9122a1610a52@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 02/22/2018 07:22 AM, David Steele wrote:
> 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.

Is there a Best Practices wiki?
(https://wiki.postgresql.org/wiki/Detailed_installation_guides is pretty old
and thin.)

--
Money Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2018-02-22 15:00:26 Re: Not sure if I should CREATE INDEX for text columns on which I plan to filter later
Previous Message David Steele 2018-02-22 13:22:04 Re: initdb when data/ folder has mount points