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

tablecmds.c

  • Tom Lane's avatar
    1e3b21dd
    Change FK trigger naming convention to fix self-referential FKs. · 1e3b21dd
    Tom Lane authored
    Use names like "RI_ConstraintTrigger_a_NNNN" for FK action triggers and
    "RI_ConstraintTrigger_c_NNNN" for FK check triggers.  This ensures the
    action trigger fires first in self-referential cases where the very same
    row update fires both an action and a check trigger.  This change provides
    a non-probabilistic solution for bug #6268, at the risk that it could break
    client code that is making assumptions about the exact names assigned to
    auto-generated FK triggers.  Hence, change this in HEAD only.  No need for
    forced initdb since old triggers continue to work fine.
    1e3b21dd
    History
    Change FK trigger naming convention to fix self-referential FKs.
    Tom Lane authored
    Use names like "RI_ConstraintTrigger_a_NNNN" for FK action triggers and
    "RI_ConstraintTrigger_c_NNNN" for FK check triggers.  This ensures the
    action trigger fires first in self-referential cases where the very same
    row update fires both an action and a check trigger.  This change provides
    a non-probabilistic solution for bug #6268, at the risk that it could break
    client code that is making assumptions about the exact names assigned to
    auto-generated FK triggers.  Hence, change this in HEAD only.  No need for
    forced initdb since old triggers continue to work fine.