Re: Alternative to \copy in psql modelled after \g
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Daniel Verite <daniel@manitou-mail.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
"David G. Johnston" <david.g.johnston@gmail.com>
Date: 2019-01-26T19:19:00Z
Lists: pgsql-hackers
Fabien COELHO <coelho@cri.ensmp.fr> writes: >> It's unclear to me whether to push ahead with Daniel's existing >> patch or not. It doesn't look to me like it's making things >> any worse from the error-consistency standpoint than they were >> already, so I'd be inclined to consider error semantics cleanup >> as something to be done separately/later. > Fine. OK. I fixed the error-cleanup issue and pushed it. The patch applied cleanly back to 9.5, but the code for \g is a good bit different in 9.4. I didn't have the interest to try to make the patch work with that, so I just left 9.4 alone. regards, tom lane
Commits
-
Fix psql's "\g target" meta-command to work with COPY TO STDOUT.
- cda1e27fb706 9.5.16 landed
- ae4c7d5ab886 9.6.12 landed
- 8e97a97b3206 10.7 landed
- 6d3ede5f1c65 12.0 landed
- 2c50c9f23d1d 11.2 landed