| 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 HEADER MATCH for COPY TO |
| Date: | 2026-11-04 01:24:13 |
| Message-ID: | OS9P286MB698308BE47EB0A13CD50D7697494682@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 MATCH as a value of the
HEADER option for both directions of COPY.
For example:
COPY t1 TO STDOUT WITH (HEADER <TAB><TAB>
false MATCH true
However, the documentation says that HEADER MATCH is valid only for
COPY FROM. If a user selects the suggested "MATCH" candidate for
COPY TO, the command fails:
COPY t1 TO STDOUT WITH (HEADER MATCH);
ERROR: cannot use "match" with HEADER in COPY TO
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 "MATCH" only
for COPY FROM. The boolean values remain available in both
directions, and the change applies to both COPY and \copy completion.
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-HEADER-MATCH-for-COPY-TO.patch | application/octet-stream | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Koshino Taiki | 2026-11-04 01:22:32 | [PATCH v1] psql: Do not complete JSON format for COPY FROM |