Fix pg_xlogdump so that it handles cross-page XLP_FIRST_IS_CONTRECORD record.
authorFujii Masao <[email protected]>
Mon, 29 Aug 2016 05:34:58 +0000 (14:34 +0900)
committerFujii Masao <[email protected]>
Mon, 29 Aug 2016 06:51:30 +0000 (15:51 +0900)
commit5833306dd691f3827ad0856246864626ab1deeb8
tree6d8a3ef93c3b684ce18a7969d586855d8ad4cb15
parent68bd9f795d49603941527d1bf357f5e74d164ece
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