feat: Retry on Postgres deadlock#21268
Conversation
|
🚀 PostgreSQL Cloud UI deployed to Vercel: |
erezrokah
left a comment
There was a problem hiding this comment.
FYI there's a test in
you can borrow to simulate many concurrent syncs
I borrowed and tuned the test but I was not quite able to repro the issue. Nevertheless, the test exercises the correct code path so I think it still has value in terms of showing how to set up a spec with |
75129d2 to
31243a1
Compare
erezrokah
left a comment
There was a problem hiding this comment.
Looks good pending adding docs for the new configuration
2b03787 to
9d1b1cc
Compare
This is flagged behind the Spec to enable incremental deployment.
This does not currently overwrite rows, but instead merely adds new ones. It will not fully reproduce the deadlock unless we can overwrite rows.
Definitely exercising the right code paths but still as yet unable to create a repro.
We weren't reproducing the deadlock and we're getting SQLSTATE 53300 (too many clients). Could run the tests sequentially but not worthwhile unless an actual repro is possible.
9d1b1cc to
188e02e
Compare
🤖 I have created a release *beep* *boop* --- ## [8.10.0](plugins-destination-postgresql-v8.9.0...plugins-destination-postgresql-v8.10.0) (2025-08-27) ### Features * Retry on Postgres deadlock ([#21268](#21268)) ([cfcffba](cfcffba)) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.89.0 ([#21238](#21238)) ([deb4cee](deb4cee)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Summary
retry_on_deadlockoption.