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

From Stephen Frost
Subject Re: INSERT times - same storage space but more fields -> much slower inserts
Date
Msg-id 20090414161534.GM8123@tamriel.snowman.net
Whole thread Raw
In response to Re: INSERT times - same storage space but more fields -> much slower inserts  (Matthew Wakeling <matthew@flymine.org>)
Responses Re: INSERT times - same storage space but more fields -> much slower inserts
List pgsql-performance
* Matthew Wakeling (matthew@flymine.org) wrote:
> On Tue, 14 Apr 2009, Stephen Frost wrote:
>> Bacula should be using COPY for the batch data loads, so hopefully won't
>> suffer too much from having the fields split out.  I think it would be
>> interesting to try doing PQexecPrepared with binary-format data instead
>> of using COPY though.  I'd be happy to help you implement a test setup
>> for doing that, if you'd like.
>
> You can always do binary-format COPY.

I've never played with binary-format COPY actually.  I'd be happy to
help test that too though.

    Thanks,

        Stephen

Attachment

pgsql-performance by date:

Previous
From: Matthew Wakeling
Date:
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts
Next
From: Craig Ringer
Date:
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts