-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: use insert ignore for filecache_extended #48564
base: master
Are you sure you want to change the base?
fix: use insert ignore for filecache_extended #48564
Conversation
The current approach is to insert a new row and, if a unique constraint violation occurs, update an existing one. PostgreSQL logs the unique constraint violation as error "duplicate key value violates unique constraint". Our Adapter.insertIgnoreConflict method provides a way to run an insert query without logging such errors by using the vendor-specific sql extensions like "on conflict do nothing" on Postgres. Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
cda4948
to
af89838
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least seems to solve the issue on 29 (without sharding)
@kesselb any chance to continue/finalize this? |
I guess, sharding support is a blocking problem? |
Yep, I wrote down my findings at #19494 (comment) and handed the ticket over to Stephan. |
The fix could applied on the older versions never the less? |
duplicate key value violates unique constraint
#19494Summary
TODO
Checklist