CODEWITHSUNDEEP
postgresql
Learner
Learner

Reputation: 287

Postgres Lock(For Update) row level locking returns value post lock

I am trying to implement rowlevel lock using below query

BEGIN;
    
SELECT * FROM public.student where student_code=1 For update;

The above query i ran in pgadmin.

Now through the application if i try to do a select the select returns a value. Ideally this should not

What am i doing wrong here?

Upvotes: 1

Views: 1914

Answers (1)

Laurenz Albe
Laurenz Albe

Reputation: 246248

This is a feature, not a bug; see the documentation:

Read Committed Isolation Level

[...]

UPDATE, DELETE, SELECT FOR UPDATE, and SELECT FOR SHARE commands behave the same as SELECT in terms of searching for target rows: they will only find target rows that were committed as of the command start time. However, such a target row might have already been updated (or deleted or locked) by another concurrent transaction by the time it is found. In this case, the would-be updater will wait for the first updating transaction to commit or roll back (if it is still in progress). If the first updater rolls back, then its effects are negated and the second updater can proceed with updating the originally found row. If the first updater commits, the second updater will ignore the row if the first updater deleted it, otherwise it will attempt to apply its operation to the updated version of the row. The search condition of the command (the WHERE clause) is re-evaluated to see if the updated version of the row still matches the search condition. If so, the second updater proceeds with its operation using the updated version of the row. In the case of SELECT FOR UPDATE and SELECT FOR SHARE, this means it is the updated version of the row that is locked and returned to the client.

After all, that is the meaning of “READ COMMITTED” – you see that latest committed version of the row..

If you want to avoid that, you can use the REPEATABLE READ isolation level. Then you get read stability, so that you only see the same state of the database for the whole transaction. In that case, you will receive a serialization error, since the row version that can be locked (the latest one) is not the one you see.

Upvotes: 2

Related Questions