WAL archive is lost - Mailing list pgsql-hackers

From matsumura.ryo@fujitsu.com
Subject WAL archive is lost
Date
Msg-id OSAPR01MB502788790877F85C7B5E0F00E8490@OSAPR01MB5027.jpnprd01.prod.outlook.com
Whole thread Raw
Responses Re: WAL archive is lost
Re: WAL archive is lost
List pgsql-hackers
Hi all

I find a situation that WAL archive file is lost but any WAL segment file is not lost.
It causes for archive recovery to fail. Is this behavior a bug?

example:

  WAL segment files
  000000010000000000000001
  000000010000000000000002
  000000010000000000000003

  Archive files
  000000010000000000000001
  000000010000000000000003

  Archive file 000000010000000000000002 is lost but WAL segment files
  is continuous. Recovery with archive (i.e. PITR) stops at the end of
  000000010000000000000001.

How to reproduce:
- Set up replication (primary and standby).
- Set [archive_mode = always] in standby.
- WAL receiver exits (i.e. because primary goes down)
  after receiver inserts the last record in some WAL segment file
  before receiver notifies the segement file to archiver(create .ready file).

Even if WAL receiver restarts, the WAL segment file is not notified to
archiver.


Regards
Ryo Matsumura



pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Next
From: Amit Langote
Date:
Subject: Re: adding partitioned tables to publications