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 Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/247c76a989097f1b4ab6fae898f24e75aa27fc1b Modified Files -------------- src/backend/access/heap/heapam.c | 202 ++++++++++++++++++++++++++++++++------ 1 file changed, 171 insertions(+), 31 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
