From: | Jonathan Rudenberg <jonathan(at)titanous(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sqlsmith] Unpinning error in parallel worker |
Date: | 2018-04-17 23:43:50 |
Message-ID: | 1524008630.2186289.1341689208.31A2DB11@webmail.messagingengine.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 17, 2018, at 19:31, Thomas Munro wrote:
> On Wed, Apr 18, 2018 at 11:01 AM, Jonathan Rudenberg
> <jonathan(at)titanous(dot)com> wrote:
> > On Tue, Apr 17, 2018, at 18:38, Thomas Munro wrote:
> >> Thanks, that would be much appreciated, as would any clues about what
> >> workload you're running. Do you know what the query plan looks like
> >> for the queries that crashed?
> >
> > Yep, I think I know approximately what it looked like, I've attached a lightly redacted plan. All of the hung queries were running some variant of this plan as far as I can tell.
>
> Hmm, that isn't a parallel query. I was expecting to see "Gather" and
> "Parallel" in there.
Oops, I'm really sorry about that. I only have the first part of the hung queries, and there are a few variants. Here's one that's parallel.
Attachment | Content-Type | Size |
---|---|---|
dsa_hang_plan_v2.txt | text/plain | 20.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2018-04-18 00:07:18 | Should we add GUCs to allow partition pruning to be disabled? |
Previous Message | Thomas Munro | 2018-04-17 23:31:33 | Re: [sqlsmith] Unpinning error in parallel worker |