Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns

Oh, Mike <minsoo@amazon.com>

From: "Oh, Mike" <minsoo@amazon.com>

To: ahsan hadi <ahsan.hadi@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>

Cc: "Drouvot, Bertrand" <bdrouvot@amazon.com>

Date: 2021-06-04T22:59:22Z

Lists: pgsql-hackers

This patch should address the same problem for pglogical as well.

Thanks,
Mike

On 6/4/21, 3:55 PM, "ahsan hadi" <ahsan.hadi@gmail.com> wrote:

    CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



    The following review has been posted through the commitfest application:
    make installcheck-world:  tested, passed
    Implements feature:       tested, passed
    Spec compliant:           tested, passed
    Documentation:            not tested

    I have also seen this error with logical replication using pglogical extension, will this patch also address similar problem with pglogical?

Commits

Fix the incorrect assertion introduced in commit 7f13ac8123.
- d2169c998553 16.0 landed
Fix catalog lookup with the wrong snapshot during logical decoding.
- 7f13ac812313 16.0 landed
- 272248a0c1b1 15.0 landed
- 68dcce247f1a 14.6 landed
- 547b963683e3 13.9 landed
- 794460783125 12.13 landed
- e721123b7a0c 11.18 landed
- bf0718c137c4 10.23 landed
Clean up assorted failures under clang's -fsanitize=undefined checks.
- 46ab07ffda9d 15.0 cited