Re: Some bugs in psql_complete of psql - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Some bugs in psql_complete of psql
Date
Msg-id CAHGQGwGB91SNyZWnLGEytRBx1Kbi0W2PO3NnH5QG0C2g6MmbdA@mail.gmail.com
Whole thread Raw
In response to Re: Some bugs in psql_complete of psql  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Some bugs in psql_complete of psql  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
On Fri, Nov 6, 2015 at 11:27 AM, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> Hello, thank you for the comments.
>
> The revised version of this patch is attached.

Thanks for updating the patch!

I tested whether the following patterns work as expected or not.

CREATE UNIQUE INDEX CONCURRENTLY name ON
CREATE UNIQUE INDEX CONCURRENTLY ON
CREATE UNIQUE INDEX name ON
CREATE UNIQUE INDEX ON
CREATE INDEX CONCURRENTLY name ON
CREATE INDEX CONCURRENTLY ON
CREATE INDEX name ON
CREATE INDEX ON

Then I found the following problems.

"CREATE UNIQUE INDEX CONCURRENTLY <tab>" didn't suggest "ON".
"CREATE UNIQUE INDEX ON <tab>" suggested nothing.
"CREATE INDEX CONCURRENTLY <tab>" didn't suggest "ON".
"CREATE INDEX ON <tab>" suggested nothing.

BTW, I found that tab-completion for DROP INDEX has the following problems.

"DROP INDEX <tab>" didn't suggest "CONCURRENTLY".
"DROP INDEX CONCURRENTLY name <tab>" suggested nothing.

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Support of partial decompression for datums
Next
From: Craig Ringer
Date:
Subject: Re: Logical replication and multimaster