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

Re: COPY insert performance

From: "Chris Isaacson" <cisaacson(at)tradebotsystems(dot)com>
To: "Gavin Sherry" <swm(at)alcove(dot)com(dot)au>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: COPY insert performance
Date: 2005-07-26 12:27:25
Message-ID: 07774C6E31D94A44A2A60E2085944F09071DF3@tbmail.tradebot.com (view raw or flat)
Thread:
Lists: pgsql-performance
I need the chunks for each table COPYed within the same transaction
which is why I'm not COPYing concurrently via multiple
threads/processes.  I will experiment w/o OID's and decreasing the
shared_buffers and wal_buffers.

Thanks,
Chris

-----Original Message-----
From: Gavin Sherry [mailto:swm(at)alcove(dot)com(dot)au] 
Sent: Tuesday, July 26, 2005 7:12 AM
To: Chris Isaacson
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] COPY insert performance


Hi Chris,

Have you considered breaking the data into multiple chunks and COPYing
each concurrently?

Also, have you ensured that your table isn't storing OIDs?

On Mon, 25 Jul 2005, Chris Isaacson wrote:

> #---------------------------------------------------------------------
> --
> ----
> # RESOURCE USAGE (except WAL)
>
#-----------------------------------------------------------------------
> ----
> shared_buffers = 65536  # min 16, at least max_connections*2, 8KB each

shared_buffers that high has been shown to affect performance. Try
12000.

> wal_buffers = 64  # min 4, 8KB each

Increasing wal_buffers can also have an effect on performance.

Thanks,

Gavin

pgsql-performance by date

Next:From: Jeff TroutDate: 2005-07-26 14:22:57
Subject: Re: COPY insert performance
Previous:From: Chris IsaacsonDate: 2005-07-26 12:23:02
Subject: Re: COPY insert performance

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