model-writtenrun 1481 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Dmitry Koval reported that a concurrent update moving a conflicting tuple between partitions could trigger an assertion during INSERT ... ON CONFLICT DO UPDATE, and supplied an injection-point reproducer plus a draft converting the assertion into an error #1.
- Joseph Koshakow reproduced the failure and proposed simply deleting the assertion so the caller could retry, reporting successful reproduction-test, CI, and local test runs #2; his subsequent historical check established that partitioned targets were already supported when the assertion was introduced #3.
- After a nine-month gap, Dmitry refreshed his error-based proposal and reproducer because the issue remained unresolved #4, then resent the unchanged fix with a new version for Commitfest #5.
- Tom Lane selected Joseph's retry-based solution because it preserved existing production behavior and matched updates within a partition, rejecting the proposed new error; he also demonstrated that SELECT FOR UPDATE could replace the injection point and make the regression test backpatchable #6.
- The fix landed as 55b5859d41, derived from #2 with an additional assertion removal and isolation tests covering concurrent updates and deletion, and was backpatched through PostgreSQL 14; Tom's final message confirmed the push, closing the thread with the error-based alternative left out #6.