pgsql: Stopgap solution for problem reported by Alexey Beschiokov: after

Started by Tom Laneover 20 years ago1 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Log Message:
-----------
Stopgap solution for problem reported by Alexey Beschiokov: after
doing heap_insert or heap_update, wipe out any extracted fields in
the TupleTableSlot containing the tuple, because they might not be valid
anymore if tuptoaster.c changed the tuple. Safe because slot must be
in the materialized state, but mighty ugly --- find a better answer!

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
pgsql/src/backend/executor:
execMain.c (r1.256.2.1 -> r1.256.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.256.2.1&r2=1.256.2.2)