Hi, A brief ping on v4 before PG20-2 starts. The latest CFBot run is green on all enabled jobs:
https://github.com/postgres/postgres-cfbot/actions/runs/32910623105/attempts/1 The point on which I would especially appreciate review is the restart_lsn invariant described in section 2 of v4: a decoding pass that does not know the subtransaction's parent cannot output-decode that transaction's commit, so tuplecid entries left by the skipped cleanup cannot reach ReorderBufferBuildTupleCidHash(). Could someone comment on whether that reasoning is sound, and whether the O(N) abort-time cleanup is an acceptable backpatchable fix? PostgreSQL 19 is currently at Beta 3. Should BUG #19555 also be tracked as a PostgreSQL 19 open item? CF entry: https://commitfest.postgresql.org/patch/7137/ Thanks, Bingshuai Li
