projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e4828e9) | patch
Use a more granular approach to follow update chains
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Wed, 27 Nov 2013 20:50:33 +0000 (17:50 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Thu, 28 Nov 2013 15:00:12 +0000 (12:00 -0300)
commit247c76a989097f1b4ab6fae898f24e75aa27fc1b
treefd5adb45900ea946da30bfd63dade5e3e6e6d2adtree
parente4828e9ccba731178dd77aed078db7ceb0e1e8d1commit | diff
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
src/backend/access/heap/heapam.c diff | blob | blame | history
This is the main PostgreSQL git repository.