| From: | Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, 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-17 08:34:59 |
| Message-ID: | a4fe3652-a0a0-4482-8a7e-15024671b53e@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/10/2023 23:21, Ashutosh Bapat wrote:
> On Mon, Oct 16, 2023 at 10:24 AM Andrei Lepikhov
> Whenever I visited this idea, I hit one issue prominently - how would
> we differentiate different scans of the non-partitioned relation.
> Normally we do that using different Relids but in this case we
> wouldn't be able to know the number of such relations involved in the
> query unless we start planning such a join. It's late to add new base
> relations and assign them new Relids. Of course I haven't thought hard
> about it. I haven't looked at the patch to see whether this problem is
> solved and how.
>
I'm curious, which type of problems do you afraid here? Why we need a
range table entry for each scan of non-partitioned relation?
--
regards,
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-10-17 08:40:00 | Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written} |
| Previous Message | shveta malik | 2023-10-17 08:31:25 | Re: Synchronizing slots from primary to standby |