1
0
mirror of https://github.com/postgres/postgres.git synced 2025-12-24 06:01:07 +03:00
Files
postgres/src
Alvaro Herrera 4c71f48f4c Use a more granular approach to follow update chains
Instead of simply checking the KEYS_UPDATED bit, we need to check
whether each lock held on the future version of the tuple conflicts with
the lock we're trying to acquire.

Per bug report #8434 by Tomonari Katsumata
2013-11-28 11:54:25 -03:00
..
2013-05-29 16:58:43 -04:00
2013-10-07 16:27:04 -04:00
2012-10-10 21:42:38 -04:00
2013-06-01 10:18:59 -04:00