On Thu, Mar 18, 2021 at 12:56:12PM +0900, Michael Paquier wrote: > I was looking at uses of ThisTimeLineID in the wild, and could not > find it getting checked or used actually in backend-side code that > involved the WAL reader facility. Even if it brings confidence, it > does not mean that it is not used somewhere :/
I have been working on that over the last couple of days, and applied a fix down to 10. One thing that I did not like in the test was the use of compare() to check if the contents of the WAL segment before and after the timeline jump remained the same as this would have been unstable with any concurrent activity. Instead, I have added a phase at the end of the test with an extra checkpoint and recovery triggered once, which is enough to reproduce the PANIC reported at the top of the thread. I'll look into clarifying the use of ThisTimeLineID within the those WAL reader callbacks, because this is really bug-prone in the long term... This requires some coordination with the recent work aimed at adding some logical decoding support in standbys, though. -- Michael
signature.asc
Description: PGP signature
