From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | strange CREATE INDEX tab completion cases |
Date: | 2015-12-12 02:17:25 |
Message-ID: | 566B83B5.8000702@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
These two tab completion pieces look strange to me:
/* If we have CREATE|UNIQUE INDEX <sth> CONCURRENTLY, then add "ON" */
else if ((pg_strcasecmp(prev3_wd, "INDEX") == 0 ||
pg_strcasecmp(prev2_wd, "INDEX") == 0) &&
pg_strcasecmp(prev_wd, "CONCURRENTLY") == 0)
COMPLETE_WITH_CONST("ON");
/* If we have CREATE|UNIQUE INDEX <sth>, then add "ON" or "CONCURRENTLY" */
else if ((pg_strcasecmp(prev3_wd, "CREATE") == 0 ||
pg_strcasecmp(prev3_wd, "UNIQUE") == 0) &&
pg_strcasecmp(prev2_wd, "INDEX") == 0)
{
static const char *const list_CREATE_INDEX[] =
{"CONCURRENTLY", "ON", NULL};
COMPLETE_WITH_LIST(list_CREATE_INDEX);
}
They appear to support a syntax along the lines of
CREATE INDEX name CONCURRENTLY
which is not the actual syntax.
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2015-12-12 02:25:36 | Disabling an index temporarily |
Previous Message | Noah Misch | 2015-12-12 02:17:12 | Re: More on the libxml2 update situation |