On Mon, 2009-06-22 at 11:24 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > I was thinking it might be beneficial to be able to defer writing WAL
> > until COPY is complete, so heap_sync would either fsync the whole heap
> > file or copy the whole file to WAL.
>
> What about indexes?
I was thinking we could do exactly as stated for the cases that would be
WAL-bypass now, but need to write WAL because XLogArchivingActive().
i.e. improve the exact case we are measuring here.
Yes, it is more complex than that for loading to existing tables.
-- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
