Re: Improve tab completion for COPY
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Nathan Bossart <nathandbossart@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-11T18:47:01Z
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 Tue, Jun 10, 2025 at 1:33 PM Nathan Bossart <nathandbossart@gmail.com> 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. > > > TBH I'd even say that 0002 is fixing a bug and could be back-patched. I've > added rmt@ here in case Tomas or Heikki feel differently. Thank you for your confirmation. I've just pushed the change (1) and am waiting for more comments on the change (2). Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com