Hi, This is apparently an EDB-owned machine but I have no access to it currently (I could ask if necessary). For some reason it's been failing for a week, but only on REL_12_STABLE, with this in the log:
2019-08-20 04:31:48.886 MDT [13421:4] LOG: server process (PID 13871) was terminated by signal 11: unrecognized signal 2019-08-20 04:31:48.886 MDT [13421:5] DETAIL: Failed process was running: SET default_table_access_method = ''; Apparently HPUX's sys_siglist doesn't recognise that most popular of signals, 11, but by googling I see that it has its traditional meaning there. That's clearly in the create_am test: 019-08-20 04:31:22.404 MDT [13871:31] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2019-08-20 04:31:22.404 MDT [13871:32] pg_regress/create_am STATEMENT: DROP ACCESS METHOD gist2; 2019-08-20 04:31:22.405 MDT [13871:33] pg_regress/create_am LOG: statement: DROP ACCESS METHOD gist2 CASCADE; 2019-08-20 04:31:22.422 MDT [13871:34] pg_regress/create_am LOG: statement: SET default_table_access_method = ''; Perhaps it was really running the next statement. It's hard to see how cdc8d371e2, the only non-doc commit listed on the first failure, could have anything to do with that. -- Thomas Munro https://enterprisedb.com