From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | ohp(at)pyrenet(dot)fr |
Cc: | pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: where is the output |
Date: | 2005-12-23 20:18:34 |
Message-ID: | 20051223201834.GA72599@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 23, 2005 at 02:19:09PM +0100, ohp(at)pyrenet(dot)fr wrote:
> But I'd still like to know in that case (the same goes for C I guess)
> where stdout is.
> Why isn't it connected by default to the input of whatever connected by
> dbconnect?
From the COPY documentation:
When STDIN or STDOUT is specified, data is transmitted via the
connection between the client and the server.
I think the names STDIN and STDOUT are causing the confusion: they're
just the server's names for the client/server connection and don't
have anything to do with the client's stdin and stdout. The client
writes data to and reads data from the connection using the API
functions for doing so; where the client gets or puts that data is
up to the application.
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2005-12-23 20:37:31 | Questions related to xlog |
Previous Message | Tom Lane | 2005-12-23 20:18:21 | Fixing row comparison semantics |