Fix pg_xlogdump so that it handles cross-page XLP_FIRST_IS_CONTRECORD record.
authorFujii Masao
Mon, 29 Aug 2016 05:34:58 +0000 (14:34 +0900)
committerFujii Masao
Mon, 29 Aug 2016 05:38:17 +0000 (14:38 +0900)
commit314a25fb3ae3ae2fc6007fd39ff01da7558565a4
tree6dc1dfd4f03873c2e8e21ee55ea6566038b94021
parent5b79dd6eddeecc656ecf5fd85a61a2a3fa170efa
Fix pg_xlogdump so that it handles cross-page XLP_FIRST_IS_CONTRECORD record.

Previously pg_xlogdump failed to dump the contents of the WAL file
if the file starts with the continuation WAL record which spans
more than one pages. Since pg_xlogdump assumed that the continuation
record always fits on a page, it could not find the valid WAL record to
start reading from in that case.

This patch changes pg_xlogdump so that it can handle a continuation
WAL record which crosses a page boundary and find the valid record
to start reading from.

Back-patch to 9.3 where pg_xlogdump was introduced.

Author: Pavan Deolasee
Reviewed-By: Michael Paquier and Craig Ringer
Discussion: CABOikdPsPByMiG6J01DKq6om2+BNkxHTPkOyqHM2a4oYwGKsqQ@mail.gmail.com
src/backend/access/transam/xlogreader.c