| From: | Koshino Taiki <koshino(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Subject: | [PATCH v1] psql: Do not complete JSON format for COPY FROM |
| Date: | 2026-11-04 01:22:32 |
| Message-ID: | OS9P286MB6983081F365ED9931EC988345D94682@OS9P286MB698308.JPNP286.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I noticed that psql's tab completion suggests the JSON format for both
directions of COPY.
For example:
COPY t1 FROM STDIN WITH (FORMAT <TAB><TAB>
binary csv json text
However, the documentation says that the JSON format is allowed only
for COPY TO. If a user selects the suggested "json" candidate, the
command fails:
COPY t1 FROM STDIN WITH (FORMAT JSON);
ERROR: COPY FORMAT JSON is not supported for COPY FROM
I think it is misleading for tab completion to suggest syntax that is
explicitly unsupported by the documentation and rejected by the
server.
The attached patch checks the COPY direction and offers "json" only
for COPY TO. This applies to both COPY and \copy completion.
There is already a separate discussion proposing support for COPY FROM
with FORMAT json [1]. If that support is committed, the completion can
of course be extended at the same time. However, in the current tree
COPY FROM does not support JSON, so I think tab completion should
reflect the currently implemented and documented behavior.
Regards,
Taiki Koshino<koshino(at)sraoss(dot)co(dot)jp>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-psql-Do-not-complete-JSON-format-for-COPY-FROM.patch | application/octet-stream | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Koshino Taiki | 2026-11-04 01:24:13 | [PATCH v1] psql: Do not complete HEADER MATCH for COPY TO |
| Previous Message | Lukas Fittl | 2026-11-04 01:19:00 | Re: Assert failure in parallel query due to SubPlan double visit for hash join |