diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-03-14 11:31:22 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-03-14 11:31:22 -0400 |
| commit | 1bee54e5143f4925297954690c56920d720b7078 (patch) | |
| tree | 25c84a2a91d3d7ce13d45dd444dab2f5929ffeee /src | |
| parent | aa9c4e71ceccf239a268b0b6611a9260d0f94a74 (diff) | |
| download | postgresql-1bee54e5143f4925297954690c56920d720b7078.tar.gz postgresql-1bee54e5143f4925297954690c56920d720b7078.zip | |
Add missing NULL terminator to list_SECURITY_LABEL_preposition[].
On the machines I tried this on, pressing TAB after SECURITY LABEL led to
being offered ON and FOR as intended, plus random other keywords (varying
across machines). But if you were a bit more unlucky you'd get a crash,
as reported by nummervet@mail.ru in bug #14019.
Seems to have been an aboriginal error in the SECURITY LABEL patch,
commit 4d355a8336e0f226. Hence, back-patch to all supported versions.
There's no bug in HEAD, though, thanks to our recent tab-completion
rewrite.
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/psql/tab-complete.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/psql/tab-complete.c b/src/bin/psql/tab-complete.c index a789f2b4c33..73fc349bf02 100644 --- a/src/bin/psql/tab-complete.c +++ b/src/bin/psql/tab-complete.c @@ -3419,7 +3419,7 @@ psql_completion(const char *text, int start, int end) pg_strcasecmp(prev_wd, "LABEL") == 0) { static const char *const list_SECURITY_LABEL_preposition[] = - {"ON", "FOR"}; + {"ON", "FOR", NULL}; COMPLETE_WITH_LIST(list_SECURITY_LABEL_preposition); } |