Hi, I have tested the v2 patches for "SERIALIZABLE can commit write skew after SSI summarization." The following are my testing results
- Reproduced the issue before applying the patches, where both serializable transactions committed and the final count became 2. - After applying the patches, PostgreSQL raised a serialization failure when the first transaction attempted to update the second row. - Verified that predicate-lock summarization occurred (locks_summarized = true) and the conflict was detected even after summarization. - Verified the final table contents: only one row had v = 1 (final count = 1). regards, solai
