From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/src/pl/plpgsql/src pl_comp.c plpg ... |
Date: | 2003-08-18 19:16:03 |
Message-ID: | 20030818191603.0D651D1B8AC@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)svr1(dot)postgresql(dot)org 03/08/18 16:16:02
Modified files:
src/pl/plpgsql/src: pl_comp.c plpgsql.h
Log message:
When compiling a plpgsql trigger function, include the OID of the table
the trigger is attached to in the hashkey. This ensures that we will
create separate compiled trees for each table the trigger is used with,
avoiding possible datatype-mismatch problems if the tables have different
rowtypes. This is essentially the same bug recently identified in plpython
--- though plpgsql doesn't seem as prone to crash when the rowtype changes
underneath it. But failing robustly is no substitute for just working.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-19 01:13:41 | pgsql-server/src backend/executor/execGrouping ... |
Previous Message | Bruce Momjian | 2003-08-18 02:52:46 | pgsql-server/doc TODO |