Re: pg_receivewal starting position - Mailing list pgsql-hackers

From Ronan Dunklau
Subject Re: pg_receivewal starting position
Date
Msg-id 22424666.6Emhk5qWAg@aivenronan
Whole thread Raw
In response to Re: pg_receivewal starting position  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: pg_receivewal starting position  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
Le mardi 26 octobre 2021, 08:27:47 CEST Ronan Dunklau a écrit :
> Yes, I will try to simplify the logic of the patch I sent last week. I'll
> keep you posted here soon.

I was able to simplify it quite a bit, by using only one standby for both test
scenarios.

This test case verify that after a timeline switch, if we resume from a
previous state we will archive:
 - segments from the old timeline
 - segments from the new timeline
 - the timeline history file itself.

I chose to check against a full segment from the previous timeline, but it
would have been possible to check that the latest timeline segment was
partial. I chose not not, in the unlikely event we promote at an exact segment
boundary. I don't think it matters much, since partial wal files are already
covered by other tests.

--
Ronan Dunklau
Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Gather performance analysis
Next
From: Dilip Kumar
Date:
Subject: Re: Gather performance analysis