Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> Unlike PQexecPrepared(...), binary-format COPY doesn't handle endian and
> type size issues for you. You need to convert the data to the database
> server's endianness and type sizes, but I don't think the PostgreSQL
> protocol provides any way to find those out.
The on-the-wire binary format is much better specified than you think.
(The documentation of it sucks, however.) It's big-endian in all cases
and the datatype sizes are well defined.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Brian Cox||Date: 2009-04-15 00:41:24|
|Subject: error updating a very large table|
|Previous:||From: Craig Ringer||Date: 2009-04-15 00:31:37|
|Subject: Re: INSERT times - same storage space but more fields ->
much slower inserts|