Re: \h tab-completion

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: \h tab-completion
Date: 2017-02-03 12:12:08
Message-ID: 93c9e87e-2199-9fe2-ed33-34ca9369e16a@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/25/2017 07:13 AM, Michael Paquier wrote:
> What I think you should do is making the code path of
> \\h smarter with some exceptions by using TailMatchesCS2() for ALTER.
> There is as well the case of DROP commands that should be treated by
> the way.

Yes, I think that is correct approach. I have attached a patch where I
add completion for \h ALTER and \h DROP.

Andreas

Attachment Content-Type Size
help-completion-v1.patch text/x-patch 3.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-02-03 12:15:16 Re: Checksums by default?
Previous Message Rafia Sabih 2017-02-03 11:07:46 Redundant comment in ExecutePlan