| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | "Andrey V(dot) 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-28 03:35:29 |
| Message-ID: | CAPmGK17s3o2W5-9L4Ljq37PXSvjw9+H-U0BPRPBGJi-YKAR3Ng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jul 27, 2021 at 8:01 PM Andrey V. Lepikhov
<a(dot)lepikhov(at)postgrespro(dot)ru> wrote:
> On 7/27/21 3:50 PM, Etsuro Fujita wrote:
> > On Tue, Jul 27, 2021 at 3:22 PM Andrey V. Lepikhov
> > <a(dot)lepikhov(at)postgrespro(dot)ru> wrote:
> >> >> Also, may be you tell your opinion about an additional optimization
> >> >> of Async Append [1]?
> >
> >> > Is the optimization related to this issue?
> >
> >> This optimization tries to postpone choice of async subplans. It allows
> >> us to make a decision on async capable subplans after all plan
> >> flattening operations.
> >
> > Thanks for the explanation! My understanding is that the optimization
> > isn’t related to this issue. Right?
> Right
OK
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-07-28 05:02:31 | Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction |
| Previous Message | Orishich Aleksey | 2021-07-28 02:17:42 | RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes |