From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: conchuela timeouts since 2021-10-09 system upgrade |
Date: | 2021-10-24 23:53:19 |
Message-ID: | 3792312.1635119599@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
>> 24 окт. 2021 г., в 19:19, Noah Misch <noah(at)leadboat(dot)com> написал(а):
>> These failures started on 2021-10-09, the day conchuela updated from DragonFly
>> v4.4.3-RELEASE to DragonFly v6.0.0-RELEASE. It smells like a kernel bug.
prairiedog just reported the identical symptom:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prairiedog&dt=2021-10-24%2016%3A05%3A58
I'm thinking "timing problem" more than "kernel bug". (I'd have also
believed "ancient IPC::Run bug", except that I assume conchuela is
running a pretty modern IPC::Run.)
I can poke into it tomorrow.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2021-10-25 00:56:36 | Re: BUG #17245: Index corruption involving deduplicated entries |
Previous Message | Noah Misch | 2021-10-24 23:35:02 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |