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

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

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: Stephen Frost <sfrost(at)snowman(dot)net>
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:01:08
Message-ID: alpine.DEB.2.00.0904141700020.4053@aragorn.flymine.org (view raw or flat)
Thread:
Lists: pgsql-performance
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.

Matthew

-- 
 An ant doesn't have a lot of processing power available to it. I'm not trying
 to be speciesist - I wouldn't want to detract you from such a wonderful
 creature, but, well, there isn't a lot there, is there?
                                        -- Computer Science Lecturer

In response to

Responses

pgsql-performance by date

Next:From: Stephen FrostDate: 2009-04-14 16:15:34
Subject: Re: INSERT times - same storage space but more fields ->much slower inserts
Previous:From: Stephen FrostDate: 2009-04-14 15:56:14
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