diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-07-02 13:35:14 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-07-02 13:35:14 -0400 |
| commit | 074add6ed286a02256a1b03137ff6dd7c8126f25 (patch) | |
| tree | a1cb1f3a2658c46415683ebf84481c2293cf8c75 /src/backend/access/gist/gist.c | |
| parent | 4b85f20f948d885875a1e1b89979e627b86e6e64 (diff) | |
| download | postgresql-074add6ed286a02256a1b03137ff6dd7c8126f25.tar.gz postgresql-074add6ed286a02256a1b03137ff6dd7c8126f25.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/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions