Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

execCurrent.c

Blame
    • Tom Lane's avatar
      9bedd128
      Add support for invoking parser callback hooks via SPI and in cached plans. · 9bedd128
      Tom Lane authored
      As proof of concept, modify plpgsql to use the hooks.  plpgsql is still
      inserting $n symbols textually, but the "back end" of the parsing process now
      goes through the ParamRef hook instead of using a fixed parameter-type array,
      and then execution only fetches actually-referenced parameters, using a hook
      added to ParamListInfo.
      
      Although there's a lot left to be done in plpgsql, this already cures the
      "if (TG_OP = 'INSERT' and NEW.foo ...)"  problem, as illustrated by the
      changed regression test.
      9bedd128
      History
      Add support for invoking parser callback hooks via SPI and in cached plans.
      Tom Lane authored
      As proof of concept, modify plpgsql to use the hooks.  plpgsql is still
      inserting $n symbols textually, but the "back end" of the parsing process now
      goes through the ParamRef hook instead of using a fixed parameter-type array,
      and then execution only fetches actually-referenced parameters, using a hook
      added to ParamListInfo.
      
      Although there's a lot left to be done in plpgsql, this already cures the
      "if (TG_OP = 'INSERT' and NEW.foo ...)"  problem, as illustrated by the
      changed regression test.