Re: A failure in 031_recovery_conflict.pl on Cirrus CI Windows Server
От | Noah Misch |
---|---|
Тема | Re: A failure in 031_recovery_conflict.pl on Cirrus CI Windows Server |
Дата | |
Msg-id | 20230725105456.GA171037@rfd.leadboat.com обсуждение исходный текст |
Ответ на | A failure in 031_recovery_conflict.pl on Cirrus CI Windows Server (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Ответы |
A failure in 031_recovery_conflict.pl on Debian/s390x
|
Список | 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@mail.gmail.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).
В списке pgsql-hackers по дате отправления: