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
    Don't think that the context "UPDATE tab SET var =" is a GUC-setting
    command.
    
    If we have "SET var =" but the "var" is not a known GUC variable,
    don't offer any completions.  The most likely explanation is that
    we've misparsed the context and it's not really a GUC-setting command.
    
    Per gripe from Ken Tanzer.  Back-patch to 9.6.  The issue exists
    further back, but before 9.6 the code looks very different and it
    doesn't actually know whether the "var" name matches anything,
    so I desisted from trying to fix it.
    
    Discussion: https://postgr.es/m/CAD3a31XpXzrZA9TT3BqLSHghdTK+=cXjNCE+oL2Zn4+oWoc=qA@mail.gmail.com
    47fe7a75
    History
    Name Last commit Last update