From: | Gavin Sherry <swm(at)alcove(dot)com(dot)au> |
---|---|
To: | Chris Isaacson <cisaacson(at)tradebotsystems(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: COPY insert performance |
Date: | 2005-07-26 12:12:21 |
Message-ID: | Pine.LNX.4.58.0507262208030.15612@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Isaacson | 2005-07-26 12:15:15 | Re: COPY insert performance |
Previous Message | Jochem van Dieten | 2005-07-26 09:58:17 | Re: "Vacuum Full Analyze" taking so long |