From: | Suraj Khamkar <khamkarsuraj(dot)b(at)gmail(dot)com> |
---|---|
To: | katouknl <katouknl(at)oss(dot)nttdata(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion |
Date: | 2021-10-06 16:57:32 |
Message-ID: | CA+U=F9iWA7_Z47p6y2U1Z60B_05XmqWeyc3bGgoMGFygsq33jg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I reviewed your patch. At a first glance, I have the below comments.
1. The below change crosses the 80-character limit in a line. Please
maintain the same.
- "LARGE OBJECT", "TABLESPACE", "TEXT SEARCH", "ROLE");
+ "LARGE OBJECT", "TABLESPACE", "TEXT SEARCH", "TRANSFORM FOR",
"ROLE");
2. There are trailing whitespaces after
COMPLETE_WITH_QUERY(Query_for_list_of_languages);.
Remove these extra whitespaces.
surajkhamkar(at)localhost:tab_comment$ git apply
fix_tab_complete_comment.patch
fix_tab_complete_comment.patch:38: trailing whitespace.
COMPLETE_WITH_QUERY(Query_for_list_of_languages);
warning: 1 line adds whitespace errors.
Regards,
Suraj Khamkar
On Wed, Sep 29, 2021 at 2:04 PM katouknl <katouknl(at)oss(dot)nttdata(dot)com> wrote:
> Hi,
>
> I created a patch for COMMENT tab completion.
> It was missing TRANSFORM FOR where it's supposed to be.
>
> Best wishes,
> Ken Kato
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-10-06 16:58:34 | Re: Running tests under valgrind is getting slower at an alarming pace |
Previous Message | Jeremy Schneider | 2021-10-06 16:56:34 | Re: pg_walinspect - a new extension to get raw WAL data and WAL stats |