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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers