Re: Improve tab completion for COPY
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Nathan Bossart <nathandbossart@gmail.com>,
Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Yugo Nagata <nagata@sraoss.co.jp>, torikoshia
<torikoshia@oss.nttdata.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>,
rmt@lists.postgresql.org
Date: 2025-06-10T23:56:48Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix tab-completion for COPY and \copy options.
- f5a987c0e5f6 19 (unreleased) landed
- 765a4c94ccc8 18.0 landed
- c1c6169eb4f4 17.6 landed
- d69836b13c46 16.10 landed
- e3584e457db2 15.14 landed
- 0514616f0e28 14.19 landed
-
Add tab completion for REJECT_LIMIT option.
- b774ad493367 18.0 landed
-
Allow "COPY table TO" command to copy rows from materialized views.
- 534874fac0b3 18.0 cited
-
Add REJECT_LIMIT option to the COPY command.
- 4ac2a9beceb1 18.0 cited
On 2025/06/11 5:33, Nathan Bossart wrote: > On Tue, Jun 10, 2025 at 12:37:48PM -0700, Masahiko Sawada wrote: >>>> (1) adds tab completion support for the REJECT_LIMIT option, which was >>>> introduced in v18 >>>> (2) splits the tab completion logic between COPY FROM and COPY TO to >>>> reflect their different options. >> >> [...] >> >> Given REJECT_LIMIT is a new v18 feature, it seems to me that (1) is an >> oversight of this feature, but I also agree that it's not a bug and >> doesn't block the release. >> >> How does the RMT feel about the change (1)? Nathan, would you be OK with that? > > 0001 sure seems like an oversight in commit 4ac2a9b to me. In any case, I > argued that we should fix tab completion for unlogged partitioned tables in > v18 [0], and this seems pretty similar. BTW, I also have a similar patch [1] in my queue that I'm planning to commit. Materialized views have been allowed in COPY TO since v18 (commit 534874fac0b), and that patch improves tab completion to include them. For the same reason discussed here, it might make sense to commit that patch in v18 as well. Regards, [1] https://postgr.es/m/CACJufxFxnSkikp+GormAGHcMTX1YH2HRXW1+3dJM9w7yY9hdsg@mail.gmail.com -- Fujii Masao NTT DATA Japan Corporation