Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> 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 outpu
Bruce Momjian <[EMAIL PROTECTED]> 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 wo
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I think the biggest problem is that stdin/stdout in COPY is different
> > from \copy. I propose we make stdin/stdout consistent for COPY and
> > \copy, where stdin always reads from command input, and stdout always
> > writes to comma
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think the biggest problem is that stdin/stdout in COPY is different
> from \copy. I propose we make stdin/stdout consistent for COPY and
> \copy, where stdin always reads from command input, and stdout always
> writes to command output. This does brea
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> No it doesn't. EOF will do fine. The source program doesn't
> >> necessarily have to know anything about COPY, as long as its output is
> >> in a format COPY can cope with (eg, tab-delimited).
>
> > The current
