| From: | Ha Ka <klasahubert(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Lukasz Biegaj <lukasz(dot)biegaj(at)unitygroup(dot)com>, Krzysztof Kois <krzysztof(dot)kois(at)unitygroup(dot)com> |
| Subject: | Re: Unresolved repliaction hang and stop problem. |
| Date: | 2021-06-16 10:53:00 |
| Message-ID: | CAKnL6DeBr8R8LcQEUmd9eKB+6GYEyDTFcnp6yPShdWzi+-iV0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
śr., 16 cze 2021 o 12:31 Lukasz Biegaj <lukasz(dot)biegaj(at)unitygroup(dot)com>
napisał(a):
> On 04.05.2021 16:35, Alvaro Herrera wrote:
> > I would suggest to do that by running the problematic
> > workload in the test system under "perf record -g"
> We'll go with both propositions. I expect to come back to you with
> results in about a week or two.
Hi Alvaro,
We reproduced the replication issue and recorded the walsender process
using perf.
Below you can find the data for broken and working replication:
password to the zip file: johS5jeewo
Please let me know if you would like us to proceed with the downgrade.
--
Hubert Klasa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2021-06-16 10:59:33 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Yagiz Nizipli | 2021-06-16 10:48:02 | Re: [PATCH] rename column if exists |