Re: initdb when data/ folder has mount points
Ron Johnson <ron.l.johnson@cox.net>
From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-general@lists.postgresql.org
Date: 2018-02-22T14:21:04Z
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.