pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Temporarily skip recovery deadlock test in back branches. 5+ messages / 1 participants [nested] [flat]
* pgsql: Temporarily skip recovery deadlock test in back branches. @ 2022-05-06 16:36 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-05-06 16:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Temporarily skip recovery deadlock test in back branches. The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f40d362a667f6cf36f17d7565e4d7565fb7910f3 Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 5 +++++ 1 file changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Temporarily skip recovery deadlock test in back branches. @ 2022-05-06 16:36 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-05-06 16:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Temporarily skip recovery deadlock test in back branches. The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4e39957e6eb52887c2d631e9edf08a07c306ec9f Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 5 +++++ 1 file changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Temporarily skip recovery deadlock test in back branches. @ 2022-05-06 16:36 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-05-06 16:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Temporarily skip recovery deadlock test in back branches. The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/26f9e21cb63e0737f6abcc106e31313ae94d3b8b Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 5 +++++ 1 file changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Temporarily skip recovery deadlock test in back branches. @ 2022-05-06 16:36 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-05-06 16:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Temporarily skip recovery deadlock test in back branches. The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14 Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fb965ab0f64198c7b97fd83e125860a0b4b944d7 Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 5 +++++ 1 file changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Temporarily skip recovery deadlock test in back branches. @ 2022-05-06 16:36 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-05-06 16:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Temporarily skip recovery deadlock test in back branches. The recovery deadlock test has a timing issue that was fixed in 5136967f1eb in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14 Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/441fa7a63ad4ed9377e08c6295b9f94f16a4e61e Modified Files -------------- src/test/recovery/t/031_recovery_conflict.pl | 5 +++++ 1 file changed, 5 insertions(+) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2022-05-06 16:36 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-05-06 16:36 pgsql: Temporarily skip recovery deadlock test in back branches. Andres Freund <andres@anarazel.de> 2022-05-06 16:36 pgsql: Temporarily skip recovery deadlock test in back branches. Andres Freund <andres@anarazel.de> 2022-05-06 16:36 pgsql: Temporarily skip recovery deadlock test in back branches. Andres Freund <andres@anarazel.de> 2022-05-06 16:36 pgsql: Temporarily skip recovery deadlock test in back branches. Andres Freund <andres@anarazel.de> 2022-05-06 16:36 pgsql: Temporarily skip recovery deadlock test in back branches. Andres Freund <andres@anarazel.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox