Re: pg9.6: no backup history file (*.backup) created on hot standby - Mailing list pgsql-general

From Michael Paquier
Subject Re: pg9.6: no backup history file (*.backup) created on hot standby
Date
Msg-id 20181009035334.GF2137@paquier.xyz
Whole thread Raw
In response to pg9.6: no backup history file (*.backup) created on hot standby  (magodo <wztdyl@sina.com>)
Responses Re: pg9.6: no backup history file (*.backup) created on hot standby  (magodo <wztdyl@sina.com>)
List pgsql-general
On Tue, Oct 09, 2018 at 11:45:50AM +0800, magodo wrote:
> Yet, I am still not so clear how does the bloat of pg_wal happen? Do
> you mean pg_wal will be filled up by many .backup(s)?

If your archive_command is for example a simple cp (which it should not
be by the way), and if you try to archive twice the same file, then the
archive command would continuously fail and prevent existing WAL
segments to be archived.  Segments are continuously created, and pg_wal
grows in size.
--
Michael

Attachment

pgsql-general by date:

Previous
From: magodo
Date:
Subject: Re: pg9.6: no backup history file (*.backup) created on hot standby
Next
From: Raghavendra Rao J S V
Date:
Subject: pg_dump: [archiver (db)] query failed: FATAL: semop(id=10649641)failed: Identifier removed