diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-02-19 14:44:58 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-02-19 14:45:17 -0500 |
commit | 761a5688b179d46091e7314458571c5fc537084a (patch) | |
tree | ba80bb48f7a3b69bffb0caadefa0346542a87800 /contrib/earthdistance/Makefile | |
parent | 2ed19a488edb3980e054e6064e7028ccb652e5df (diff) | |
download | postgresql-761a5688b179d46091e7314458571c5fc537084a.tar.gz |
Fix confusion about event trigger vs. plain function in plpgsql.
The function hash table keys made by compute_function_hashkey() failed
to distinguish event-trigger call context from regular call context.
This meant that once we'd successfully made a hash entry for an event
trigger (either by validation, or by normal use as an event trigger),
an attempt to call the trigger function as a plain function would
find this hash entry and thereby bypass the you-can't-do-that check in
do_compile(). Thus we'd attempt to execute the function, leading to
strange errors or even crashes, depending on function contents and
server version.
To fix, add an isEventTrigger field to PLpgSQL_func_hashkey,
paralleling the longstanding infrastructure for regular triggers.
This fits into what had been pad space, so there's no risk of an ABI
break, even assuming that any third-party code is looking at these
hash keys. (I considered replacing isTrigger with a PLpgSQL_trigtype
enum field, but felt that that carried some API/ABI risk. Maybe we
should change it in HEAD though.)
Per bug #16266 from Alexander Lakhin. This has been broken since
event triggers were invented, so back-patch to all supported branches.
Discussion: https://postgr.es/m/16266-fcd7f838e97ba5d4@postgresql.org
Diffstat (limited to 'contrib/earthdistance/Makefile')
0 files changed, 0 insertions, 0 deletions