Re: failures in t/031_recovery_conflict.pl on CI
От | Tom Lane |
---|---|
Тема | Re: failures in t/031_recovery_conflict.pl on CI |
Дата | |
Msg-id | 1929823.1651549472@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: failures in t/031_recovery_conflict.pl on CI (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: failures in t/031_recovery_conflict.pl on CI
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > I ended up committing the extension of the test first, before the fix. I think > that's the cause of the failure on longfin on serinus. Let's hope the > situation improves with the now also committed (and backpatched) fix. longfin's definitely not very happy: four out of six tries have ended with psql:<stdin>:8: ERROR: canceling statement due to conflict with recovery LINE 1: SELECT * FROM test_recovery_conflict_table2; ^ DETAIL: User was holding shared buffer pin for too long. timed out waiting for match: (?^:User transaction caused buffer deadlock with recovery.) at t/031_recovery_conflict.pl line358. I can poke into that tomorrow, but are you sure that that isn't an expectable result? regards, tom lane
В списке pgsql-hackers по дате отправления: