Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: COPY insert performance
- 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: Tue, 26 Jul 2005 22:12:21 +1000 (EST)
- Message-id: <Pine.LNX.4.58.0507262208030.15612@linuxworld.com.au> <text/plain>
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
- References:
- COPY insert performance
- From: Chris Isaacson
- COPY insert performance
- Prev by Date: Re: "Vacuum Full Analyze" taking so long
- Next by Date: Re: COPY insert performance
- Previous by thread: Re: COPY insert performance
- Next by thread: Re: COPY insert performance
- Indexes: