From: Tom Lane <tgl@sss.pgh.pa.us>
To: sbernikov@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17054: Memory corruption in logical replication worker when
 replicating into partitioned table
In-reply-to: <1819098.1623369807@sss.pgh.pa.us>
References: <17054-637193af919f0024@postgresql.org>
 <1819098.1623369807@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Thu, 10 Jun 2021 20:03:27 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2061770.1623443489.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Jun 2021 16:31:29 -0400
Message-ID: <2061771.1623443489@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2061771.1623443489%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> When logical replication target is a partitioned table then execution o=
f any
>> DDL on source table leads to crash of target (subscriber) server.

> Thanks for the report!  I duplicated the crash on v13 branch tip,

I can't reproduce this anymore after commit b270713fd.  I think it's
probably the same thing I found while making a test for your other
report:

    logicalrep_partition_open() failed to ensure that the
    LogicalRepPartMapEntry it built for a partition was fully
    independent of that for the partition root, leading to
    trouble if the root entry was later freed or rebuilt.

My failure to see a crash on HEAD was probably an accidental
issue of memory reuse patterns.

			regards, tom lane