Re: INSERT times - same storage space but more fields -> much slower inserts

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
(view: Whole thread, Raw)
In response to: Re: INSERT times - same storage space but more fields -> much slower inserts  (Craig Ringer)
List: pgsql-performance


Craig Ringer <> 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:

From: Stephen Frost
Date:
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: error updating a very large table