On Mon, Jan 30, 2017 at 12:29 PM, David Steele <da...@pgmasters.net> wrote: > The solution was to simply ignore the checksums of any pages with an LSN >>= the LSN returned by pg_start_backup(). This means that hot blocks > may never be checked during backup, but if they are active then any > problems should be caught directly by PostgreSQL.
I feel like this doesn't fix the problem. Suppose the backup process reads part of a block that hasn't been modified in a while, and then PostgreSQL writes the block, and then the backup process reads the rest of the block. The LSN test will not prevent the checksum from being verified, but the checksum will fail to match. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
