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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Previously, you could partition by a boolean column as long as you
    spelled the bound values as string literals, for instance FOR VALUES
    IN ('t').  The trouble with this is that ruleutils.c printed that as
    FOR VALUES IN (TRUE), which is reasonable syntax but wasn't accepted by
    the grammar.  That results in dump-and-reload failures for such cases.
    
    Apply a minimal fix that just causes TRUE and FALSE to be converted to
    strings 'true' and 'false'.  This is pretty grotty, but it's too late for
    a more principled fix in v11 (to say nothing of v10).  We should revisit
    the whole issue of how partition bound values are parsed for v12.
    
    Amit Langote
    
    Discussion: https://postgr.es/m/e05c5162-1103-7e37-d1ab-6de3e0afaf70@lab.ntt.co.jp
    1222db99
    History
    Name Last commit Last update