| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Krzysztof Kois <krzysztof(dot)kois(at)unitygroup(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unresolved repliaction hang and stop problem. |
| Date: | 2021-04-14 10:19:51 |
| Message-ID: | CAA4eK1KLtCHGn_8e07HsyjggkjoR68SQkpJr-a9ZtA3Q2oC_0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 13, 2021 at 1:18 PM Krzysztof Kois
<krzysztof(dot)kois(at)unitygroup(dot)com> wrote:
>
> Hello,
> After upgrading the cluster from 10.x to 13.1 we've started getting a problem describe pgsql-general:
> https://www.postgresql.org/message-id/8bf8785c-f47d-245c-b6af-80dc1eed40db%40unitygroup.com
> We've noticed similar issue being described on this list in
> https://www.postgresql-archive.org/Logical-replication-CPU-bound-with-TRUNCATE-DROP-CREATE-many-tables-tt6155123.html
> with a fix being rolled out in 13.2.
>
The fix for the problem discussed in the above threads is committed
only in PG-14, see [1]. I don't know what makes you think it is fixed
in 13.2. Also, it is not easy to back-patch that because this fix
depends on some of the infrastructure introduced in PG-14.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Himanshu Upadhyaya | 2021-04-14 10:45:27 | Re: [PATCH] PREPARE TRANSACTION unexpected behavior with TEMP TABLE |
| Previous Message | Amit Kapila | 2021-04-14 10:01:13 | Re: Truncate in synchronous logical replication failed |