| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| 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 06:16:39 |
| Message-ID: | 20180222061639.GB3370@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2018-02-22 08:57:26 | Re: Not sure if I should CREATE INDEX for text columns on which I plan to filter later |
| Previous Message | Pawan Sharma | 2018-02-22 06:00:33 | Re: oracle to postgresql conversion tool |