On 2/3/17 07:12, Andreas Karlsson wrote: > 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.
Instead of creating another copy of list_ALTER, let's use the words_after_create list and write a version of create_command_generator/drop_command_generator. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
