pgsql: Stopgap solution for problem reported by Alexey Beschiokov: after - Mailing list pgsql-committers

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!

Modified Files:
--------------
    pgsql/src/backend/executor:
        execMain.c (r1.258 -> r1.259)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.258&r2=1.259)