| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>,"Voillequin, Jean-Marc" <Jean-Marc(dot)Voillequin(at)moodys(dot)com>,"pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15535: psql: \copy: parse error at... |
| Date: | 2018-12-05 17:23:19 |
| Message-ID: | 8116df5b-46d4-4099-b334-bd727e337044@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote:
> There was a proposal awhile back to provide a variant of \copy
> that works more like \g, so you'd enter something like
>
> COPY (SELECT ...) TO STDOUT
> \copyto somefile
>
> which'd be way more flexible --- the COPY command wouldn't have to
> fit on one line, for one thing. But I don't think that's gone
> anywhere yet.
That would be the proof-of-concept patch posted a few weeks ago here:
https://www.postgresql.org/message-id/15dadc39-e050-4d46-956b-dcc4ed098753@manitou-mail.org
There didn't seem to be much of community buy-in for this idea, so I've it
let rest
for the moment. On one hand, it solves actual problems such as the one
mentioned in this bug report, on the other hand I can feel the discomfort
of having 3 forms of \copy, in addition to COPY, and that maybe it would
create more confusion than benefits, overall.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-05 17:32:55 | Re: BUG #15535: psql: \copy: parse error at... |
| Previous Message | Voillequin, Jean-Marc | 2018-12-05 15:21:57 | RE: BUG #15535: psql: \copy: parse error at... |