Re: stdin/stdout mismatch for COPY and \copy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: stdin/stdout mismatch for COPY and \copy
Date
Msg-id 27542.1081534855@sss.pgh.pa.us
Whole thread Raw
In response to Re: stdin/stdout mismatch for COPY and \copy  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: stdin/stdout mismatch for COPY and \copy  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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 "-".
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: stdin/stdout mismatch for COPY and \copy
Next
From: Neil Conway
Date:
Subject: FYI: MIT Innovation Lab 2004