| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Dept of second thoughts: after studying index_getnext() a bit |
| Date: | 2009-11-01 22:31:02 |
| Message-ID: | 20091101223102.C2C08753FB7@cvs.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-11-03 07:53:58 | pgsql: Fix obscure segfault condition in PL/Python In PLy_output(), |
| Previous Message | Tom Lane | 2009-11-01 22:30:54 | pgsql: Dept of second thoughts: after studying index_getnext() a bit |