| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | sbernikov(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17054: Memory corruption in logical replication worker when replicating into partitioned table |
| Date: | 2021-06-11 20:31:29 |
| Message-ID: | 2061771.1623443489@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> When logical replication target is a partitioned table then execution of 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zlatoslav Petukhov | 2021-06-11 21:09:45 | Re: BUG #17057: Unexpected error: ERROR: unsupported target type: 0 |
| Previous Message | Tom Lane | 2021-06-11 20:15:20 | Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti |