I've been looking at the recent spate of intermittent failures on my Cygwin animal lorikeet. Most of them look something like this, where there's 'VACUUM FULL pg_class' and an almost simultaneous "CREATE TABLE' which fails.
2021-06-14 05:04:00.220 EDT [60c71b7f.e8bf:60] pg_regress/vacuum LOG: statement: VACUUM FULL pg_class; 2021-06-14 05:04:00.222 EDT [60c71b80.e8c0:7] pg_regress/typed_table LOG: statement: CREATE TABLE persons OF person_type; 2021-06-14 05:04:00.232 EDT [60c71b80.e8c1:3] pg_regress/inherit LOG: statement: CREATE TABLE a (aa TEXT); *** starting debugger for pid 59584, tid 9640 2021-06-14 05:04:14.678 EDT [60c71b53.e780:4] LOG: server process (PID 59584) exited with exit code 127 2021-06-14 05:04:14.678 EDT [60c71b53.e780:5] DETAIL: Failed process was running: CREATE TABLE persons OF person_type; 2021-06-14 05:04:14.678 EDT [60c71b53.e780:6] LOG: terminating any other active server processes Getting stack traces in this platform can be very difficult. I'm going to try forcing complete serialization of the regression tests (MAX_CONNECTIONS=1) to see if the problem goes away. Any other suggestions might be useful. Note that we're not getting the same issue on REL_13_STABLE, where the same group pf tests run together (inherit typed_table, vacuum) cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
