On 06/23/2017 12:11 AM, Tom Lane wrote: > Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes: >> On 06/22/2017 10:24 AM, Tom Lane wrote: >>> That earlier request is still valid. Also, if you can reproduce the >>> symptom that lorikeet just showed and get a stack trace from the >>> (hypothetical) postmaster core dump, that would be hugely valuable. >> See attached log and stacktrace > The stacktrace seems to be from the parallel-query-leader backend. > Was there another core file? > > The lack of any indication in the postmaster log that the postmaster saw > the parallel worker's crash sure looks the same as lorikeet's failure. > But if the postmaster didn't dump core, then we're still at a loss as to > why it didn't respond. > >
Rerunning with some different settings to see if I can get separate cores. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
