Re: COPY insert performance
От | Chris Isaacson |
---|---|
Тема | Re: COPY insert performance |
Дата | |
Msg-id | 07774C6E31D94A44A2A60E2085944F09071DF3@tbmail.tradebot.com обсуждение исходный текст |
Ответ на | COPY insert performance ("Chris Isaacson" <cisaacson@tradebotsystems.com>) |
Список | 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@alcove.com.au] Sent: Tuesday, July 26, 2005 7:12 AM To: Chris Isaacson Cc: pgsql-performance@postgresql.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 по дате отправления: