| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: A failure in 031_recovery_conflict.pl on Cirrus CI Windows Server |
| Date: | 2023-07-25 10:54:56 |
| Message-ID: | 20230725105456.GA171037@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 25, 2023 at 01:56:41PM +0530, Bharath Rupireddy wrote:
> I've observed the following failure once in one of my Cirrus CI runs
> on Windows Server on HEAD:
>
> timed out waiting for match: (?^:User was holding shared buffer pin
> for too long) at
> C:/cirrus/src/test/recovery/t/031_recovery_conflict.pl line 318.
> # Postmaster PID for node "primary" is 696
>
> https://api.cirrus-ci.com/v1/artifact/task/5272062399348736/testrun/build/testrun/recovery/031_recovery_conflict/log/regress_log_031_recovery_conflict
>
> https://github.com/BRupireddy/postgres/runs/15296698158
Known:
https://postgr.es/m/flat/20220409045515.35ypjzddp25v72ou%40alap3.anarazel.de
https://postgr.es/m/flat/CA+hUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO=nEYKSg(at)mail(dot)gmail(dot)com
A good next step would be patch "Fix recovery conflict SIGUSR1 handling" from
https://postgr.es/m/CA+hUKG+Hi5P1j_8cVeqLLwNSVyJh4RntF04fYWkeNXfTrH2MYA@mail.gmail.com
(near the end of that second thread).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-07-25 11:35:31 | Re: [PATCH] Check more invariants during syscache initialization |
| Previous Message | Amit Kapila | 2023-07-25 10:47:51 | Re: logicalrep_message_type throws an error |