Re: COPY TO STDOUT BINARY

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: COPY TO STDOUT BINARY
Date: 2005-12-30 23:15:27
Message-ID: 200512302315.jBUNFR911545@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andreas Pflug wrote:
> Tom Lane wrote:
> > Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> >
> >>Is COPY foo TO STDOUT BINARY supposed to work?
> >
> >
> > I don't think psql will do anything particularly sane with binary copy
> > data, if that's what you meant.
>
> echo "COPY foo TO STDOUT BINARY;" | psql >bar
>
> writes a 0 bytes file; not surprised if psql doesn't act sanely in
> interactive mode.
>
> For testing, I changed slony to use COPY .. BINARY, same result.

I tested this in a stand-alone backend and saw binary output that looked
right, so I think it is only psql that is failing.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message BFRACI 2005-12-31 00:53:32 Re: BUG #2102: Backend reports wrong number of affected rows for a
Previous Message Chander Ganesan 2005-12-30 21:57:15 BUG #2137: CREATE DATABASE permission is not inherited.