From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: COPY BINARY to STDOUT |
Date: | 2000-06-13 07:56:24 |
Message-ID: | 2538.960882984@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Any comments on this?
There is a test in there now to reject COPY BINARY TO STDOUT/FROM STDIN.
If anyone figures out how to support it, the test can be removed...
regards, tom lane
>> SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp> writes:
>>>> postgres=# copy binary test to stdout; <====== error???
>>>> [ psql gets confused ]
>>
>> Yes, I see it too. The COPY data protocol is fundamentally textual,
>> so there's no way of making this work without rewriting all our frontend
>> interface libraries. Not worth it. I suggest that the backend should
>> reject COPY BINARY commands that are either FROM STDIN or TO STDOUT.
>> Anybody see a better way?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-13 07:58:43 | Re: Proposal for fixing numeric type-resolution issues |
Previous Message | Dmitry samersoff | 2000-06-13 07:55:18 | Re: C++ disabled by default |