From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Don Seiler <don(at)seiler(dot)us> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgBackRest backup from standby |
Date: | 2018-02-19 20:53:29 |
Message-ID: | 7f539f04-579c-1118-e5f1-85049869987c@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/19/18 3:41 PM, Don Seiler wrote:
> On Mon, Feb 19, 2018 at 10:17 AM, David Steele <david(at)pgmasters(dot)net
> <mailto:david(at)pgmasters(dot)net>> wrote:
>
> If pg_log is symlinked to PGDATA it will be copied. pg_xlog is not
> copied in any backup.
>
>
> So an external pg_log directory symlinked into $PGDATA will have its log
> contents copied?
Yes.
> I'm curious, why even copy the pg_log logs? They aren't needed for
> database restore or recovery.
The general philosophy is to copy everything except what we know for
sure can be excluded. In practice, this means sticking to what
pg_basebackup excludes because that list is vetted by the community.
Also, relocating the log directory is easy using the log_directory
setting, so that's what I recommend if it's an issue. Some users do
want to backup their logs.
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-02-19 20:54:29 | Re: Error when compiling postgresql 9.6.7 with Visual Studio 15.5.6 |
Previous Message | Don Seiler | 2018-02-19 20:41:45 | Re: pgBackRest backup from standby |