Re: stdin/stdout mismatch for COPY and \copy

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> What is "command output" and how does that differ from stdout?
>
> > In this case, stdout is going to psql's stdout, not to the command
> > stdout.
>
> Hm, I didn't realize it worked like that. So "command output" means
> "where SELECT output would go"? Is that what happens to COPY TO STDOUT?
> (experiments ... I guess so.)
>
> > I thought pstdin/pstdout were very clear in helping folks remember how
> > it is different from stdin/stdout.
>
> Fair enough. If we need two flavors of stdout too, then I agree that
> names are better than "-".

OK, the attached patch implements pstdin and pstdout, and change stdin
and stdout for \copy to be the same as COPY. Using this file:

drop table test;
create table test (x int);
insert into test values (1);
\copy test from stdin

I get for stdin:

$ psql -f /tmp/x -o /dev/null test

for pstdin:

$ psql -f /tmp/x -o /dev/null test
Enter data to be copied followed by a newline.
End with a backslash and a period on a line by itself.
test> 33
test> \.

for stdout:

$ psql -f /tmp/x -o /dev/null test

for pstdout:

$ psql -f /tmp/x -o /dev/null test
1

This breaks backward compatibility and has to be mentioned in the
release notes.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073