| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record |
| Date: | 2019-11-06 04:41:20 |
| Message-ID: | 20191106044120.GF1604@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 06, 2019 at 07:40:48AM +0500, Andrey Lepikhov wrote:
> I found this in our multimaster project on PostgreSQL 11.5. It is difficult
> to reproduce this error, but I will try to do it if necessary.
>
> The rest of a continuation WAL-record can exactly match the block size. In
> this case, we need to switch targetPagePtr to the next block before
> calculating the starting point of the next WAL-record.
> See the patch in attachment for the bug fix.
What's the error you actually saw after reading the record in
xlogreader.c? If you have past WAL archives, perhaps you are able to
reproduce the problem with a given WAL segment and pg_waldump?
This code rings a bell as of this thread which led to commit bab7823:
https://www.postgresql.org/message-id/CABOikdPsPByMiG6J01DKq6om2+BNkxHTPkOyqHM2a4oYwGKsqQ@mail.gmail.com
Reminds me as well of the following:
https://www.postgresql.org/message-id/CAOR=d=16x+jKM=00AoEZEKU9RJDwjU9E2bUnFBpX_HrGjkMHXg@mail.gmail.com
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Lepikhov | 2019-11-06 05:06:55 | Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record |
| Previous Message | Andrey Lepikhov | 2019-11-06 02:40:48 | The XLogFindNextRecord() routine find incorrect record start point after a long continuation record |