-
Notifications
You must be signed in to change notification settings - Fork 38
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
Lock contention #461
Comments
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
May 19, 2023
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
May 20, 2023
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
May 20, 2023
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
May 20, 2023
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
May 20, 2023
frodrigo
added a commit
to frodrigo/osmose-frontend
that referenced
this issue
Jul 5, 2023
frodrigo
added a commit
that referenced
this issue
Jul 16, 2023
Use latter upsert in transaction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I dig a little bit to understand why we got lock contention between insert .. on conflict ... update.
Here is a quick example :
Then :
I extracted a transaction from the log extract.log :
First, we got a begin:
Later, the session took a transaction id (xid=323772555) :
Then we had thousand insert etc
Later, another session tried to insert a record without success:
This session remained stuck until transaction 323772555 had been commited :
Both sessions tried to update the same record :
Unfortunately, this record was already locked line 110:
You should rethink processing to avoid insert line by line. It is not efficient.
One idea could be :
FYI, I created these indexes to cover foreign key :
(this is not related to this issue)
The text was updated successfully, but these errors were encountered: