Re: stdin/stdout mismatch for COPY and \copy

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(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 20:41:26
Message-ID: 200404092041.i39KfQ005321@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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 "-".

We could get away with using '-' for stdin and stdout because we know by
the "to"/"from" which it is, but again, the use of a synonym is
confusing.

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2004-04-09 21:55:45 Re: PostgreSQL configuration
Previous Message Kevin Brown 2004-04-09 20:35:26 Re: PostgreSQL configuration

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2004-04-09 23:51:26 Re: COPY for CSVs
Previous Message Tom Lane 2004-04-09 19:32:06 Re: pg_restore ignore error patch