| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Prevent ExecInsert() and ExecUpdate() from scribbling on the |
| Date: | 2005-11-14 17:42:56 |
| Message-ID: | 20051114174256.C35DED8A5B@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Prevent ExecInsert() and ExecUpdate() from scribbling on the result tuple
slot of the topmost plan node when a trigger returns a modified tuple.
These appear to be the only places where a plan node's caller did not
treat the result slot as read-only, which is an assumption that nodeUnique
makes as of 8.1. Fixes trigger-vs-DISTINCT bug reported by Frank van Vugt.
Modified Files:
--------------
pgsql/src/backend/executor:
execMain.c (r1.256 -> r1.257)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.256&r2=1.257)
execUtils.c (r1.126 -> r1.127)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execUtils.c.diff?r1=1.126&r2=1.127)
pgsql/src/include/nodes:
execnodes.h (r1.139 -> r1.140)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.139&r2=1.140)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-14 17:43:14 | pgsql: Prevent ExecInsert() and ExecUpdate() from scribbling on the |
| Previous Message | James William Pye | 2005-11-14 16:52:39 | python - ip: Add db:methodname to <tt> elements and style changes. |