On Wed, Nov 9, 2011 at 9:06 AM, Heikki Linnakangas <heikki.linnakan...@iki.fi> wrote: > In COPY, insert tuples to the heap in batches. > > This greatly reduces the WAL volume, especially when the table is narrow. > The overhead of locking the heap page is also reduced. Reduced WAL traffic > also makes it scale a lot better, if you run multiple COPY processes at > the same time.
Sounds good. I can't see where this applies backup blocks. If it does, can you document why/where/how it differs from other WAL records? There's no need for conflict processing on replay with this new WAL record type. But you should document that and alter the comments that say it is necessary. Search "conflict". -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
