| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: In COPY, insert tuples to the heap in batches. |
| Date: | 2011-11-09 13:25:46 |
| Message-ID: | CA+U5nMLeWrdDJK32AhCzdpshrHhDNdew1ppBiu+AOpwnCnNBPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Nov 9, 2011 at 9:06 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-11-09 16:15:02 | pgsql: Fix compiler warning. |
| Previous Message | Heikki Linnakangas | 2011-11-09 09:06:59 | pgsql: In COPY, insert tuples to the heap in batches. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2011-11-09 13:26:31 | Re: Syntax for partitioning |
| Previous Message | Robert Haas | 2011-11-09 13:15:23 | a modest improvement to get_object_address() |