| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: intermittent failures in Cygwin from select_parallel tests |
| Date: | 2017-06-23 04:11:06 |
| Message-ID: | 16415.1498191066@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-23 04:33:33 | Re: Guarding against bugs-of-omission in initdb's setup_depend |
| Previous Message | Chapman Flack | 2017-06-23 04:08:55 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |