Re: conchuela timeouts since 2021-10-09 system upgrade
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>, 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-14T01:24:54Z
Lists: pgsql-bugs
On Sun, Nov 14, 2021 at 1:17 PM Noah Misch <noah@leadboat.com> wrote: > On Sat, Nov 13, 2021 at 11:47:43PM +0500, Andrey Borodin wrote: > > I've adapted 7f580aa to functionality of REL_11 using "\if 0 = :client_id" metacommand. > > I really do not like idea of supporting background_pgbench() in older branches without counterpart in newer branches. > > But so far I didn't come up with some clever mutex idea for REL_10. > > That's a reasonable sentiment, but removing background_pgbench() isn't going > to fix 017_shm.pl. I'm not enthusiastic about any fix that repairs > src/bin/pgbench without repairing 017_shm.pl. I'm okay with skipping affected > test files on dragonfly >= 6 if you decide to cease figuring out how to make > them pass like the others do. Hmm, so if "IPC::Run got stuck when it should have been reaping that zombie", what's it stuck in, I guess select() or waitpid()? Maybe there' s a kernel bug but it seems hard to believe that a Unix system would have bugs in such fundamental facilities and still be able to build itself and ship a release... Otherwise I guess Perl, or perl scripts, would need to be confusing fds or pids or something? But that's hard to believe on its own, too, given the lack of problems on other systems that are pretty similar. If Andrey can still reproduce this, it'd be interesting to see a gdb backtrace, and also "ps O wchan" or perhaps kill -INFO $pid, and lsof for the process (or according to old pages found with google, perhaps the equivalent tool is "fstat" on that system).
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