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

trigger.c

Blame
    • Tom Lane's avatar
      d8d42989
      Fix collations when we call transformWhereClause from outside the parser. · d8d42989
      Tom Lane authored
      Previous patches took care of assorted places that call transformExpr from
      outside the main parser, but I overlooked the fact that some places use
      transformWhereClause as a shortcut for transformExpr + coerce_to_boolean.
      In particular this broke collation-sensitive index WHERE clauses, as per
      report from Thom Brown.  Trigger WHEN and rule WHERE clauses too.
      
      I'm not forcing initdb for this fix, but any affected indexes, triggers,
      or rules will need to be dropped and recreated.
      d8d42989
      History
      Fix collations when we call transformWhereClause from outside the parser.
      Tom Lane authored
      Previous patches took care of assorted places that call transformExpr from
      outside the main parser, but I overlooked the fact that some places use
      transformWhereClause as a shortcut for transformExpr + coerce_to_boolean.
      In particular this broke collation-sensitive index WHERE clauses, as per
      report from Thom Brown.  Trigger WHEN and rule WHERE clauses too.
      
      I'm not forcing initdb for this fix, but any affected indexes, triggers,
      or rules will need to be dropped and recreated.