Re: The case when AsyncAppend exists also in the qual of Async ForeignScan

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
Date: 2021-07-08 08:32:54
Message-ID: CAPmGK16+rUqSAWHCMzOazXMXwjWvnHe1b71bBd1aeuc8wgK8+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jul 8, 2021 at 5:06 PM Andrey Lepikhov
<a(dot)lepikhov(at)postgrespro(dot)ru> wrote:
> Initially I cought this bug during TPC-H benchmarking, query Q16, right
> after start of execution.
> Key thing here is using a hashed subplan.

The plan I got also uses a hashed SubPlan; moreover, the plan is the
same as the one shown in your patch.

Best regards,
Etsuro Fujita

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-07-08 08:33:07 BUG #17094: FailedAssertion at planner.c
Previous Message Andrey Lepikhov 2021-07-08 08:06:46 Re: The case when AsyncAppend exists also in the qual of Async ForeignScan