aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeSubplan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2003-08-18 19:16:02 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2003-08-18 19:16:02 +0000
commit23e10843db588928e18bd58018c2e70f4548f177 (patch)
tree9f3d51033ce6d56f3c3069d40030a145830df726 /src/backend/executor/nodeSubplan.c
parent141490354e5a1156039c58dfdd02a6a97d28ba4b (diff)
downloadpostgresql-23e10843db588928e18bd58018c2e70f4548f177.tar.gz
postgresql-23e10843db588928e18bd58018c2e70f4548f177.zip
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.
Diffstat (limited to 'src/backend/executor/nodeSubplan.c')
0 files changed, 0 insertions, 0 deletions