Re: Asynchronous Append on postgres_fdw nodes.

From: David Steele <david(at)pgmasters(dot)net>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Date: 2020-03-04 14:56:55
Message-ID: 1db062e4-12b7-2cf5-fa10-b6747e666656@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Georgios Kokolatos 2020-03-04 15:02:58 Re: ALTER TEXT SEARCH DICTIONARY tab completion
Previous Message David Steele 2020-03-04 14:41:16 Re: Some improvements to numeric sqrt() and ln()