Re: COPY BINARY to STDOUT

Started by Bruce Momjianalmost 26 years ago2 messageshackers
Jump to latest
#1Bruce Momjian
bruce@momjian.us

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
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#1)

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

Show quoted text

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?