Fix bugs in SSI tuple locking. 1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed wrong offset number. heapTuple->t_self is set to the tid of the first tuple in the chain that's visited, not the one actually being read.
2. CheckForSerializableConflictIn() uses the tuple's t_ctid field instead of t_self to check for exiting predicate locks on the tuple. If the tuple was updated, but the updater rolled back, t_ctid points to the aborted dead tuple. Reported by Hannu Krosing. Backpatch to 9.1. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/903784337d2531ce40fbdd10f0acd6333c6e1e44 Modified Files -------------- src/backend/access/heap/heapam.c | 4 +++- src/backend/storage/lmgr/predicate.c | 4 ++-- 2 files changed, 5 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
