| From: | Krzysztof Kois <krzysztof(dot)kois(at)unitygroup(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Unresolved repliaction hang and stop problem. |
| Date: | 2021-04-13 07:36:33 |
| Message-ID: | DB8PR10MB36126BC0DC3570637FDFED12EB4F9@DB8PR10MB3612.EURPRD10.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
After the 13.2 release, we've upgraded to it and unfortunately this did not solve the issue - the replication still stalls just as described in the original issue.
Please advise, how to debug and solve this issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-04-13 07:39:58 | Re: Simplify backend terminate and wait logic in postgres_fdw test |
| Previous Message | Michael Paquier | 2021-04-13 07:34:23 | Re: [PATCH] force_parallel_mode and GUC categories |