From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | magodo <wztdyl(at)sina(dot)com> |
Cc: | Postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg9.6: no backup history file (*.backup) created on hot standby |
Date: | 2018-10-09 02:45:04 |
Message-ID: | 20181009024504.GB2137@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
(Please do not forget to add the community mailing list in CC.)
On Tue, Oct 09, 2018 at 10:33:56AM +0800, magodo wrote:
> Since the backup history aims to aid administrator to identify the
> point from which wal archive should be kept and before which the
> archive could be cleaned. It is very helpful in kinds of use cases.
>
> Why not also create it when do basebackup on standby?
The backup_label file is equally helpful, and backup history files are
not mandatory for backups. One of the reasons behind why we cannot have
those on standbys is that there is no actual way to ensure the
uniqueness of this file, as two backups could be started in parallel
with the same start location and the *same* file name. If an archive
command is not able to handle correctly the duplicates, you could bloat
pg_wal. And that's a real problem.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | magodo | 2018-10-09 03:45:50 | Re: pg9.6: no backup history file (*.backup) created on hot standby |
Previous Message | Adrian Klaver | 2018-10-08 23:36:53 | Re: FTS trigger works 1 at a time, but fails with bulk insert script |