From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "COPY foo FROM STDOUT" and ecpg |
Date: | 2013-02-26 16:40:58 |
Message-ID: | 3312.1361896858@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 26.02.2013 18:23, Tom Lane wrote:
>> (I assume
>> the backend will bounce the other cases at some post-grammar stage.)
> No. All four combinations of FROM/TO and STDIN/STDOUT are accepted:
Huh. That seems like an odd decision. If we agree that that behavior
is desirable, then your patch is ok as-is, though I do question whether
this should be tested in the grammar at all rather than at runtime.
I wonder whether this is just an oversight, or if we did it
intentionally because people were confused about which combinations
to use. It seems like maybe "TO STDIN" could be justified if you
thought about stdin of the recipient rather than stdout of the server,
but it still seems a bit sloppy thinking.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-02-26 16:41:51 | Re: pg_xlogdump |
Previous Message | Andres Freund | 2013-02-26 16:38:14 | Re: pg_xlogdump |