Re: Reduce WAL logging of INSERT SELECT - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Reduce WAL logging of INSERT SELECT
Date
Msg-id 4E3D6648.7020807@enterprisedb.com
Whole thread Raw
In response to Re: Reduce WAL logging of INSERT SELECT  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Reduce WAL logging of INSERT SELECT
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: cataloguing NOT NULL constraints
Next
From: Jaime Casanova
Date:
Subject: Re: Reduce WAL logging of INSERT SELECT