On Thu, Jan 4, 2018 at 11:00 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Also, what the devil is happening on skink?
I looked at the server log for the first of the two skink failures. The key lines seem to be: 2018-01-04 07:45:36.764 UTC [5a4ddb98.5a97:154] LOG: statement: DROP SCHEMA testschema CASCADE; 2018-01-04 07:45:36.922 UTC [5a4ddb98.5a97:155] LOG: statement: DROP ROLE regress_tablespace_user1; 2018-01-04 07:45:36.941 UTC [5a4ddb98.5a97:156] LOG: statement: DROP ROLE regress_tablespace_user2; 2018-01-04 07:45:36.963 UTC [5a4ddb98.5a97:157] LOG: disconnection: session time: 0:00:08.472 user=andres database=regression host=[local] ...lines from other backends indicating new connections... 2018-01-04 07:45:37.289 UTC [5a4ddb92.2b65:4] LOG: server process (PID 23191) exited with exit code 128 2018-01-04 07:45:37.290 UTC [5a4ddb92.2b65:5] LOG: terminating any other active server processes So, skink is apparently dying during shutdown of a user-connected backend, and specifically the one that executed the 'tablespace' test. That test itself passed, but then afterward the backend fell over and died horribly. Interestingly, I see multiple other messages in the logs indicating similar failures: 2018-01-04 07:45:37.821 UTC [5a4ddb92.2b65:6] LOG: statistics collector process (PID 20842) exited with exit code 128 2018-01-04 07:46:08.113 UTC [5a4ddb92.2b65:9] LOG: server process (PID 29128) exited with exit code 128 2018-01-04 07:46:08.293 UTC [5a4ddb92.2b65:11] LOG: statistics collector process (PID 29059) exited with exit code 128 2018-01-04 07:46:26.384 UTC [5a4ddb92.2b65:14] LOG: server process (PID 13787) exited with exit code 128 2018-01-04 07:46:27.122 UTC [5a4ddb92.2b65:16] LOG: statistics collector process (PID 13776) exited with exit code 128 This is a valgrind animal. I don't know if that might be related somehow. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
