| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: should we have a fast-path planning for OLTP starjoins? |
| Date: | 2025-12-21 02:08:47 |
| Message-ID: | aUdWr5yPOQdXzAqD@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 20, 2025 at 05:49:24PM -0500, Bruce Momjian wrote:
> What Robert is saying in the above paragraph is even more complex ---
> that we might want to use an index on the fact table for a merge join of
> a stage 2 or 3 join, and then do the other joins. How would we detect
> this? Could we run each join on its own and see which ones choose merge
> join, and move them to stage 1?
Thinking some more, how likely would we do a merge join before applying
a restrictive join?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | zengman | 2025-12-21 02:48:07 | Re: Inline non-SQL SRFs using SupportRequestSimplify |
| Previous Message | Alena Rybakina | 2025-12-20 23:36:42 | Re: Vacuum statistics |