0

In our application two activites are running concurrent-

  • Bulk updates activity
  • Transactional activity

When both these activites are perfomed on same record cocurrently we see invalid values.

To prevent this I am thinking of using pessimistic locking(Postgres row level lock). But the issue here is I may have to lock all records for bulk updates.

  • There is not enough detail here to provide an answer. PostgreSQL locks rows automatically when the row is modified. How are you handling transactions, what are you seeing in the values that makes it "invalid"? – jjanes Dec 31 '22 at 02:09

0 Answers0