All we need is an easy explanation of the problem, so here it is.
I’m trying to understand how Postgresql under the hood is implementing a row lock so that I understand what resource implication this has.
If there are two database transactions. One of them has locked a row. The other database transaction is waiting to release the lock on that row. The transaction which is waiting for the release what resources will this consume?
Background: I would like to understand whether the waiting has a real impact on the resource consumption or whether such a lock situation provides just slow responses to the client.
How to solve :
I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.
The waiting session will hold on to all memory resources it’s acquired so far; it will consume very little CPU, sleeping while waiting on the lock; and no I/O.
Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂