Skip site navigation (1) Skip section navigation (2)

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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Matthew Wakeling <matthew(at)flymine(dot)org>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>,"pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: INSERT times - same storage space but more fields ->much slower inserts
Date: 2009-04-14 16:15:34
Message-ID: 20090414161534.GM8123@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-performance
* Matthew Wakeling (matthew(at)flymine(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Craig RingerDate: 2009-04-15 00:31:37
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts
Previous:From: Matthew WakelingDate: 2009-04-14 16:01:08
Subject: Re: INSERT times - same storage space but more fields -> much slower inserts

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group