| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Mark Feit <mfeit+postgresql(at)notonthe(dot)net> |
| Subject: | Re: stdin/stdout mismatch for COPY and \copy |
| Date: | 2004-04-09 18:20:55 |
| Message-ID: | 27542.1081534855@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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 "-".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2004-04-09 19:26:26 | FYI: MIT Innovation Lab 2004 |
| Previous Message | Bruce Momjian | 2004-04-09 18:11:20 | Re: stdin/stdout mismatch for COPY and \copy |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-04-09 18:56:23 | pg_restore ignore error patch |
| Previous Message | Bruce Momjian | 2004-04-09 18:11:20 | Re: stdin/stdout mismatch for COPY and \copy |