From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, 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-07 07:37:00 |
Message-ID: | CAHGQGwG23CD3qmW3XXh6bOfn2ogzuh=K_4ZgaKLpYCejhn_Xgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Nov 7, 2019 at 12:41 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Thu, Nov 07, 2019 at 02:41:29AM +0900, Fujii Masao wrote:
> > I created the problematic WAL file artificially by using
> > pg_logical_emit_message() and sucessfully reproduced
> > the error.
>
> Good idea. I didn't know this one.
>
> > I attached the WAL file that I created. You can
> > reproduce the issue by
> >
> > pg_waldump 000000010000000000000008 -s 0/08002028
>
> Assertion failure reproduced here.
>
> > The patch looks good to me. Barrying any objection, I will commit it.
> > XLogFindNextRecord() must return the valid record starting position,
> > but currently could return the starting position of WAL page
> > (not valid WAL record) in the case that you described. This is
> > the cause of the issue.
>
> No issues from here, thanks for taking care of it.
Thanks for the check! I committed the patch!
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-11-07 07:52:32 | Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record |
Previous Message | Dilip Kumar | 2019-11-07 05:31:17 | Re: Reorderbuffer crash during recovery |