Simon Riggs <si...@2ndquadrant.com> writes:
> Following patch writes a new WAL record that just says "copy foo to
> newts" and during replay we flush buffers and then re-execute the copy
> (but only when InArchiveRecovery). So the copy happens locally on the
> standby, not copying from primary to standby. We do this just with a
> little refactoring and a simple new WAL message.
And what happens to crash-recovery replay? You can't have it both ways,
either the data is in WAL or it's missing.
> Objections?
This is NOT the time to be rushing in marginal performance
optimizations. I don't think you've thought through all the corner
cases anyway.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
