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

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Stopgap solution for problem reported by Alexey Beschiokov: after
Date: 2005-11-19 20:57:45
Message-ID: 20051119205745.21F07DBA5F@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-11-19 20:58:42 pgsql: Stopgap solution for problem reported by Alexey Beschiokov: after
Previous Message Tom Lane 2005-11-19 19:44:55 pgsql: Change array comparison rules to consider dimensionality