Re: conchuela timeouts since 2021-10-09 system upgrade
Andrey Borodin <x4mmm@yandex-team.ru>
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
Michael Paquier <michael@paquier.xyz>,
Tom Lane <tgl@sss.pgh.pa.us>,
Peter Geoghegan <pg@bowt.ie>,
Andres Freund <andres@anarazel.de>
Date: 2021-11-10T05:49:33Z
Lists: pgsql-bugs
> 10 нояб. 2021 г., в 09:15, Noah Misch <noah@leadboat.com> написал(а): > > On Thu, Oct 28, 2021 at 07:56:00PM -0700, Noah Misch wrote: >> On Sun, Oct 24, 2021 at 09:03:27PM +0300, Andrey Borodin wrote: >>>> 24 окт. 2021 г., в 19:19, Noah Misch <noah@leadboat.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. >>>> Since the theorized kernel bug seems not to affect >>>> src/test/subscription/t/015_stream.pl, I wonder if we can borrow a workaround >>>> from other tests. One thing in common with src/test/recovery/t/017_shm.pl and >>>> the newest failure sites is that they don't write anything to the child stdin. >> >>>> If not, does passing the script via stdin, like "pgbench -f- >>>> <script.sql", work around the problem? >>> >>> I'll test it tomorrow, the refactoring does not seem trivial given we use many simultaneous scripts. >> >> Did that work? Commit 7f580aa should make this unnecessary for v12+ >> contrib/amcheck tests, but older branches still need a fix, and 017_shm.pl >> needs a fix in all branches. A backup plan is just to skip affected tests on >> dragonfly 6+. Since the breakage has been limited to so few tests, I'm >> optimistic that a better workaround will present itself. > > Is this still in your queue, or not? The conchuela breakage in > src/test/recovery and v11+v10 src/bin/pgbench is a large source of buildfarm > noise right now. Uh, sorry, this problem fell out of my attention somehow. I'll try to do something with 10 and 11 this or next week. Best regards, Andrey Borodin.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve contrib/amcheck's tests for CREATE INDEX CONCURRENTLY.
- b1f943d2aa7e 14.1 landed
- 7f580aa5d88a 15.0 landed
- 5a4b8a8a720c 13.5 landed
- 141cd0ef0b0b 12.9 landed
-
Fix minor memory leaks in pg_dump.
- 70bef494000e 15.0 cited
-
Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY.
- e428699cb3be 9.6.24 landed
- db86746fd11e 10.19 landed
- 5141e471b36a 11.14 landed
- dde966efb286 14.1 landed
- 2e33b43599ad 13.5 landed
- 0869e53d3a07 12.9 landed
- fdd965d074d4 15.0 landed
-
Fix CREATE INDEX CONCURRENTLY for the newest prepared transactions.
- df6158139f64 11.14 landed
- 560124a37c2f 10.19 landed
- 5184932432b4 9.6.24 landed
- fe5d44a1d38f 12.9 landed
- a9d0a5409415 13.5 landed
- a5b9a0000e14 14.1 landed
- 3cd9c3b92197 15.0 landed
-
Add -w back to the flags for pg_ctl (re)start in PostgresNode
- b33259e261ae 15.0 cited
-
Fix CREATE INDEX CONCURRENTLY for simultaneous prepared transactions.
- 77a0e14f0b21 9.5.25 landed
- d683d6528dba 9.6.21 landed
- 179775135b41 10.16 landed
- d1ab4bf6ed2d 11.11 landed
- be843ce29737 12.6 landed
- 86a5b309c933 13.2 landed
- 8a54e12a38d1 14.0 landed