3 ms·

There definitely was braindead locking behavior on PostgreSQL at least once: http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg157869.html http://www.

• einhverfr 14y ago
  That certainly is odd behavior however reading through the whole email thread that seems to be one complicated issue with a two processes obtaining different locks to the same row. Probably not ideal, but maybe I need to recalibrate my definition of braindead because in real-world examples, that would be highly annoying.
  • epimenov 14y ago
    It happened to us in the real world. And was fixed in 9.2
    • einhverfr 14y ago
      ouch. Reminds me of the (one) data corruption bug I found in PostgreSQL 7.3, allowing me to create write-only tables....
    • jeltz 14y ago
      Actually it is not fixed yet, the patch was pushed to 9.3 and Alvaro is still working on it. It has happened to us too, though it was very easily fixed in our case due to the excellent deadlock reporting. And I can also confirm that the case for Joel (the original reporter) is also a real world case. Link to talk about it http://www.pgcon.org/2012/schedule/events/483.en.html http://www.pgcon.org/2012/schedule/events/483.en.html Edit: Not sure if I would call it braindead though. Highly annoying, yes. Alvaro has spent a lot of time into solving this, it is much harder than it initially seems.