model-writtenrun 131 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Zsolt Parragi reported that parallel TID range rescans with changing bounds returned counts of 50, 50, and 50 instead of 50, 150, and 200 because the shared block range survived reinitialization #1.
- Zsolt's patch reset both shared bound fields to InvalidBlockNumber during reinitialization and added a regression test exercising different bounds on successive rescans #1.
- shihao zhong reproduced the failure, verified the fix, and agreed that reinitialization was the right place to reset bounds because their query dependence was new in PostgreSQL 19 #2.
- David Rowley committed the patch unchanged as ba51d62be4, retaining the implementation and regression coverage from #1.
- David closed the thread by confirming the master push and an adapted PostgreSQL 19 backport accommodating its non-atomic bound fields, leaving no outstanding patch work #3.