BUG #5048: psql: \g doesn't redirect COPY TO STDOUT, but redirects next query

Started by Andrew Deryabinover 16 years ago2 messagesbugs
Jump to latest
#1Andrew Deryabin
andrew@deryabin.com

The following bug has been logged online:

Bug reference: 5048
Logged by: Andrew Deryabin
Email address: andrew@deryabin.com
PostgreSQL version: 8.4
Operating system: FreeBSD
Description: psql: \g doesn't redirect COPY TO STDOUT, but redirects
next query
Details:

[pgsql@localhost:site]=# COPY (SELECT 1) TO STDOUT \g filename.ext
1
Time: 0.370 ms
[pgsql@localhost:site]=# SELECT 2;
Time: 0.290 ms
[pgsql@localhost:site]=# SELECT 3;
?column?
----------
3
(1 row)

Time: 0.295 ms
^Z
$ cat filename.ext
?column?
----------
2
(1 row)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andrew Deryabin (#1)
Re: BUG #5048: psql: \g doesn't redirect COPY TO STDOUT, but redirects next query

"Andrew Deryabin" <andrew@deryabin.com> writes:

[pgsql@localhost:site]=# COPY (SELECT 1) TO STDOUT \g filename.ext

The way you're supposed to do that is with \copy.
It might be more consistent to do it as above, but I'm not sure
anyone will take the time to make it happen ...

regards, tom lane