Re: [PATCH] XLogReadRecord returns pointer to currently read page

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