On 2022-09-29 17:18, Polina Bungina wrote:
> I agree with your suggestions, so here is the updated version of
> patch. Hope I haven't missed anything.
>
> Regards,
> Polina Bungina
Thanks for working on this!
It seems like we are also facing the same issue.
I tested the v3 patch under our condition, old primary has succeeded to
become new standby.
BTW when I used pg_rewind-removes-wal-segments-reproduce.sh attached in
[1], old primary also failed to become standby:
FATAL: could not receive data from WAL stream: ERROR: requested WAL
segment 000000020000000000000007 has already been removed
However, I think this is not a problem: just adding restore_command
like below fixed the situation.
echo "restore_command = '/bin/cp `pwd`/newarch/%f %p'" >>
oldprim/postgresql.conf
Attached modified reproduction script for reference.
[1]https://www.postgresql.org/message-id/CAFh8B%3DnNiFZOAPsv49gffxHBPzwmZ%3D6Msd4miMis87K%3Dd9rcRA%40mail.gmail.com
--
Regards,
--
Atsushi Torikoshi
NTT DATA CORPORATION