Re: pg9.6: no backup history file (*.backup) created on hot standby

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 03:53:34
Message-ID: 20181009035334.GF2137@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raghavendra Rao J S V 2018-10-09 05:31:04 pg_dump: [archiver (db)] query failed: FATAL: semop(id=10649641) failed: Identifier removed
Previous Message magodo 2018-10-09 03:45:50 Re: pg9.6: no backup history file (*.backup) created on hot standby