aboutsummaryrefslogtreecommitdiff
path: root/src/common/file_utils.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-07-02 13:35:14 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-07-02 13:35:14 -0400
commit4f3648de2a0bcd6eae89cb5cb0d177a672c9e239 (patch)
treee145312dfe8e39e4d7232629641184e0167ca332 /src/common/file_utils.c
parentd4b090f54fe8147157485b2c9b7753731e611354 (diff)
downloadpostgresql-4f3648de2a0bcd6eae89cb5cb0d177a672c9e239.tar.gz
postgresql-4f3648de2a0bcd6eae89cb5cb0d177a672c9e239.zip
Fix tab completion of "SET variable TO|=" to not offer bogus completions.
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
Diffstat (limited to 'src/common/file_utils.c')
0 files changed, 0 insertions, 0 deletions