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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] XLogReadRecord returns pointer to currently read page
Date: 2018-08-17 03:55:21
Message-ID: 20180817035521.GF1693@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Lepikhov 2018-08-17 04:25:57 Re: [PATCH] XLogReadRecord returns pointer to currently read page
Previous Message Andrey Lepikhov 2018-08-17 03:47:15 [PATCH] XLogReadRecord returns pointer to currently read page