Re: tab_complete for copy(merge - Mailing list pgsql-hackers

From jian he
Subject Re: tab_complete for copy(merge
Date
Msg-id CACJufxFemAs-XyOtm_to1MDB7qMZwi1ZiTPO3mmAB19owdL=tA@mail.gmail.com
Whole thread Raw
In response to Re: tab_complete for copy(merge  (Kirill Reshke <reshkekirill@gmail.com>)
List pgsql-hackers
On Tue, Nov 19, 2024 at 5:20 PM Kirill Reshke <reshkekirill@gmail.com> wrote:
>
>
> Hi!
>
> On Tue, 19 Nov 2024, 14:08 jian he, <jian.universality@gmail.com> wrote:
>>
>> hi.
>>
>> in v17, we support COPY(MERGE RETURNING)
>> we can add tab_complete for it.
>
>
> Sounds sane
>>
>>     /* Complete COPY ( with legal query commands */
>>     else if (Matches("COPY|\\copy", "("))
>> -               COMPLETE_WITH("SELECT", "TABLE", "VALUES", "INSERT
>> INTO", "UPDATE", "DELETE FROM", "WITH");
>> +               COMPLETE_WITH("SELECT", "TABLE", "VALUES", "INSERT
>> INTO", "UPDATE", "DELETE FROM", "WITH", "MERGE INTO");
>
> MERGE INTO?
>

per Synopsis
https://www.postgresql.org/docs/current/sql-merge.html
it should be "MERGE INTO".



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
Next
From: Dmitry Dolgov
Date:
Subject: Re: Changing shared_buffers without restart