From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PoC] Asynchronous execution again (which is not parallel) |
Date: | 2015-12-16 12:34:25 |
Message-ID: | CA+TgmoY2n8kyZWVjp6D0Nzw7Ra+k8asy1ZvJew-GAw=KG6TdHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 16, 2015 at 1:34 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Yes, thats one thing I wanted to know, yet another point which is not
> clear to me about this Async infrastructure is why the current
> infrastructure
> of Parallelism can't be used to achieve the Async benefits of ForeignScan?
Well, all a ForeignScan by postgres_fdw does is read the tuples that
are generated remotely. Turning around and sticking those into a
Funnel doesn't seem like it gains much: now instead of having to read
tuples from someplace, the leader has to read tuples from some other
place. Yeah, there are cases where it could win, like when there's a
selective nonpushable qual, but that's not that exciting.
There's another, more serious problem: if the leader has a connection
open to the remote server and that connection is in mid-transaction,
you can't have a worker open a new connection without changing the
semantics. Working around that problem looks hard to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-12-16 12:35:50 | Re: pg_stat_replication log positions vs base backups |
Previous Message | Stas Kelvich | 2015-12-16 12:26:35 | Re: Cube extension kNN support |