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

copy.c

  • Tom Lane's avatar
    b339d1ff
    Fire non-deferred AFTER triggers immediately upon query completion, · b339d1ff
    Tom Lane authored
    rather than when returning to the idle loop.  This makes no particular
    difference for interactively-issued queries, but it makes a big difference
    for queries issued within functions: trigger execution now occurs before
    the calling function is allowed to proceed.  This responds to numerous
    complaints about nonintuitive behavior of foreign key checking, such as
    http://archives.postgresql.org/pgsql-bugs/2004-09/msg00020.php, and
    appears to be required by the SQL99 spec.
    Also take the opportunity to simplify the data structures used for the
    pending-trigger list, rename them for more clarity, and squeeze out a
    bit of space.
    b339d1ff
    History
    Fire non-deferred AFTER triggers immediately upon query completion,
    Tom Lane authored
    rather than when returning to the idle loop.  This makes no particular
    difference for interactively-issued queries, but it makes a big difference
    for queries issued within functions: trigger execution now occurs before
    the calling function is allowed to proceed.  This responds to numerous
    complaints about nonintuitive behavior of foreign key checking, such as
    http://archives.postgresql.org/pgsql-bugs/2004-09/msg00020.php, and
    appears to be required by the SQL99 spec.
    Also take the opportunity to simplify the data structures used for the
    pending-trigger list, rename them for more clarity, and squeeze out a
    bit of space.