From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
Cc: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Aleksander Alekseev <afiskon(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, KaiGai Kohei <kaigai(at)heterodb(dot)com>, "a(dot)rybakina" <a(dot)rybakina(at)postgrespro(dot)ru>, Белялов Дамир Наилевич <d(dot)belyalov(at)postgrespro(dot)ru> |
Subject: | Re: Asymmetric partition-wise JOIN |
Date: | 2023-10-15 10:25:41 |
Message-ID: | CAPpHfdvwp7cBWs=iBv7zc7e9NOWQf0TmcwNNzw=--H1qFoBcNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Oct 15, 2023 at 8:40 AM Andrei Lepikhov
<a(dot)lepikhov(at)postgrespro(dot)ru> wrote:
> Thanks for such detailed feedback!
> The rationale for this patch was to give the optimizer additional ways
> to push down more joins into foreign servers. And, because of
> asynchronous append, the benefit of that optimization was obvious.
> Unfortunately, we hadn't found other applications for this feature,
> which was why this patch was postponed in the core.
> You have brought new ideas about applying this idea locally. Moreover,
> the main issue of the patch was massive memory consumption in the case
> of many joins and partitions - because of reparameterization. But now,
> postponing the reparameterization proposed in the thread [1] resolves
> that problem and gives some insights into the reparameterization
> technique of some fields, like lateral references.
> Hence, I think we can restart this work.
> The first thing here (after rebase, of course) is to figure out and
> implement in the cost model cases of effectiveness when asymmetric join
> would give significant performance.
Great! I'm looking forward to the revised patch.
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2023-10-15 16:25:18 | Re: pg_upgrade's interaction with pg_resetwal seems confusing |
Previous Message | Erki Eessaar | 2023-10-15 07:22:59 | Re: PostgreSQL domains and NOT NULL constraint |