Commit 2d01ec07 authored by Andrew Dunstan's avatar Andrew Dunstan

Remove unnecessary use of trigger flag to hash plperl functions

parent 84c123be
...@@ -113,7 +113,7 @@ typedef struct plperl_proc_desc ...@@ -113,7 +113,7 @@ typedef struct plperl_proc_desc
/********************************************************************** /**********************************************************************
* For speedy lookup, we maintain a hash table mapping from * For speedy lookup, we maintain a hash table mapping from
* function OID + trigger flag + user OID to plperl_proc_desc pointers. * function OID + user OID to plperl_proc_desc pointers.
* The reason the plperl_proc_desc struct isn't directly part of the hash * The reason the plperl_proc_desc struct isn't directly part of the hash
* entry is to simplify recovery from errors during compile_plperl_function. * entry is to simplify recovery from errors during compile_plperl_function.
* *
...@@ -127,11 +127,6 @@ typedef struct plperl_proc_desc ...@@ -127,11 +127,6 @@ typedef struct plperl_proc_desc
typedef struct plperl_proc_key typedef struct plperl_proc_key
{ {
Oid proc_id; /* Function OID */ Oid proc_id; /* Function OID */
/*
* is_trigger is really a bool, but declare as Oid to ensure this struct
* contains no padding
*/
Oid is_trigger; /* is it a trigger function? */
Oid user_id; /* User calling the function, or 0 */ Oid user_id; /* User calling the function, or 0 */
} plperl_proc_key; } plperl_proc_key;
...@@ -1959,7 +1954,6 @@ compile_plperl_function(Oid fn_oid, bool is_trigger) ...@@ -1959,7 +1954,6 @@ compile_plperl_function(Oid fn_oid, bool is_trigger)
/* Try to find function in plperl_proc_hash */ /* Try to find function in plperl_proc_hash */
proc_key.proc_id = fn_oid; proc_key.proc_id = fn_oid;
proc_key.is_trigger = is_trigger;
proc_key.user_id = GetUserId(); proc_key.user_id = GetUserId();
proc_ptr = hash_search(plperl_proc_hash, &proc_key, proc_ptr = hash_search(plperl_proc_hash, &proc_key,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment