Re: stdin/stdout mismatch for COPY and \copy
От | Bruce Momjian |
---|---|
Тема | Re: stdin/stdout mismatch for COPY and \copy |
Дата | |
Msg-id | 200404092041.i39KfQ005321@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: stdin/stdout mismatch for COPY and \copy (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Tom Lane wrote: > 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 "-". 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@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: