Postgres Pro
Downloads
Home   >   mailing lists

Re: INSERT times - same storage space but more fields -> much slower inserts - Mailing list pgsql-performance

From Tom Lane
Subject Re: INSERT times - same storage space but more fields -> much slower inserts
Date
Msg-id 25350.1239756009@sss.pgh.pa.us
Whole thread Raw
In response to Re: INSERT times - same storage space but more fields -> much slower inserts  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-performance
Tree view 
Craig Ringer <craig@postnewspapers.com.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

pgsql-performance by date:

Previous
From: Craig Ringer
Date:
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts
Next
From: Brian Cox
Date:
Subject: error updating a very large table