| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce WAL logging of INSERT SELECT |
| Date: | 2011-08-06 16:05:28 |
| Message-ID: | 4E3D6648.7020807@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06.08.2011 13:13, Simon Riggs wrote:
> I think we should remove the COPY optimisation because of this and
> definitely not extend INSERT SELECT to perform it automatically.
It can be very helpful when loading a lot of data, so I'm not in favor
of removing it altogether. Maybe WAL-log the first 10000 rows or such
normally, and skip WAL after that. Of course, loading 10001 rows becomes
the worst case then, but something along those lines...
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2011-08-06 16:13:27 | Re: Reduce WAL logging of INSERT SELECT |
| Previous Message | Tom Lane | 2011-08-06 15:05:58 | Re: cataloguing NOT NULL constraints |