Re: [PATCH] XLogReadRecord returns pointer to currently read page - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] XLogReadRecord returns pointer to currently read page
Date
Msg-id 20180817035521.GF1693@paquier.xyz
Whole thread Raw
In response to [PATCH] XLogReadRecord returns pointer to currently read page  (Andrey Lepikhov <a.lepikhov@postgrespro.ru>)
Responses Re: [PATCH] XLogReadRecord returns pointer to currently read page
List pgsql-hackers
On Fri, Aug 17, 2018 at 08:47:15AM +0500, Andrey Lepikhov wrote:
> Previously, in all cases of using WAL this was not a problem. However if you
> plan to perform some decoding operations before returning the WAL record to
> the caller (this is my case), this can lead to bugs that are difficult to
> catch.

What kind of cases with logical decoding are you referring to?  If
any of them can be reproduced with upstream, could you send a
reproducer, or a way to see it?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Andrey Lepikhov
Date:
Subject: [PATCH] XLogReadRecord returns pointer to currently read page
Next
From: Andrey Lepikhov
Date:
Subject: Re: [PATCH] XLogReadRecord returns pointer to currently read page