Re: Asynchronous Append on postgres_fdw nodes.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: david(at)pgmasters(dot)net
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Date: 2020-03-05 00:14:39
Message-ID: 20200305.091439.2026815663852456910.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Wed, 4 Mar 2020 09:56:55 -0500, David Steele <david(at)pgmasters(dot)net> wrote in
> On 2/28/20 3:06 AM, Kyotaro Horiguchi wrote:
> > Hello, this is a follow-on of [1] and [2].
> > Currently the executor visits execution nodes one-by-one. Considering
> > sharding, Append on multiple postgres_fdw nodes can work
> > simultaneously and that can largely shorten the respons of the whole
> > query. For example, aggregations that can be pushed-down to remote
> > would be accelerated by the number of remote servers. Even other than
> > such an extreme case, collecting tuples from multiple servers also can
> > be accelerated by tens of percent [2].
> > I have suspended the work waiting asyncrohous or push-up executor to
> > come but the mood seems inclining toward doing that before that to
> > come [3].
> > The patchset consists of three parts.
>
> Are these improvements targeted at PG13 or PG14? This seems to be a
> pretty big change for the last CF of PG13.

It is targeted at PG14. As we have the target version in CF-app now,
I marked it as targetting PG14.

Thank you for the suggestion.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2020-03-05 00:30:32 Re: [PATCH] Incremental sort
Previous Message David G. Johnston 2020-03-05 00:00:58 Re: Allowing ALTER TYPE to change storage strategy