Re: psql and COPY BINARY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: psql and COPY BINARY
Date
Msg-id 22082.1134581061@sss.pgh.pa.us
Whole thread Raw
In response to Re: psql and COPY BINARY  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: psql and COPY BINARY  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgsql-hackers
Andreas Pflug <pgadmin@pse-consulting.de> writes:
> Tom Lane wrote:
>> There wasn't any obvious bang for the buck in rewriting it.

> Well a non-binary copy could take as much as 5 times as much as a binary 
> copy. I hit this when COPYing 1.5GB of data, getting a 6.6GB file. This 
> made the 100MBit LAN connection a bottleneck.

Or vice versa --- the binary format is *not* necessarily smaller than text.
As an example, an integer column that contains only small values (say 1
or 2 digits) will need 8 bytes as binary and only 2 or 3 as text.

Fixing psql to handle binary copy isn't an unreasonable thing to do,
but I can't get real excited about it either ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: psql and COPY BINARY
Next
From: Andreas Pflug
Date:
Subject: Re: Immodest Proposal: pg_catalog.pg_ddl