Log Message:
-----------
Dept of second thoughts: after studying index_getnext() a bit more I realize
that it can scribble on scan->xs_ctup.t_self while following HOT chains,
so we can't rely on that to stay valid between hashgettuple() calls.
Introduce a private variable in HashScanOpaque, instead.
Tags:
----
REL8_4_STABLE
Modified Files:
--------------
pgsql/src/backend/access/hash:
hash.c (r1.112.2.1 -> r1.112.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hash.c?r1=1.112.2.1&r2=1.112.2.2)
hashsearch.c (r1.57 -> r1.57.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashsearch.c?r1=1.57&r2=1.57.2.1)
pgsql/src/include/access:
hash.h (r1.93.2.1 -> r1.93.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/hash.h?r1=1.93.2.1&r2=1.93.2.2)
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
