Any comments on this?


> SAKAIDA Masaaki <sakaida@psn.co.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?
> 
> 			regards, tom lane
> 


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Tue, 13 Jun 2000 03:38:54 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: COPY BINARY to STDOUT
Bruce Momjian <pgman@candle.pha.pa.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@psn.co.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?

Tue, 13 Jun 2000 03:56:24 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: COPY BINARY to STDOUT 