From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Batching in executor |
Date: | 2025-09-30 02:11:30 |
Message-ID: | CA+HiwqF-31mmZ2hhnBLuWpu1UYTVPXoEzKBW6wrf96KpY=AU7A@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Tomas,
Thanks a lot for your comments and benchmarking.
I plan to reply to your detailed comments and benchmark results, but I
just realized I had forgotten to attach patch 0008 (oops!) in my last
email. That patch adds batched qual evaluation.
I also noticed that the batched path was unnecessarily doing early
“batch-materialization” in cases like SELECT count(*) FROM bar. I’ve
fixed that as well. It was originally designed to avoid such
materialization, but I must have broken it while refactoring.
Attachment | Content-Type | Size |
---|---|---|
v2-0008-WIP-Add-ExecQualBatch-and-EEOPs-for-batched-quals.patch | application/octet-stream | 22.8 KB |
v2-0006-WIP-Add-EEOP_AGG_PLAIN_TRANS_BATCH_ROWLOOP.patch | application/octet-stream | 21.5 KB |
v2-0007-WIP-Add-EEOP_AGG_PLAIN_TRANS_BATCH_DIRECT.patch | application/octet-stream | 11.2 KB |
v2-0005-WIP-Add-EEOPs-and-helpers-for-TupleBatch-processi.patch | application/octet-stream | 16.9 KB |
v2-0004-WIP-Add-agg_retrieve_direct_batch-for-plain-aggre.patch | application/octet-stream | 6.3 KB |
v2-0001-Add-batch-table-AM-API-and-heapam-implementation.patch | application/octet-stream | 13.7 KB |
v2-0003-Executor-add-ExecProcNodeBatch-and-integrate-SeqS.patch | application/octet-stream | 9.0 KB |
v2-0002-SeqScan-add-batch-driven-variants-returning-slots.patch | application/octet-stream | 27.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2025-09-30 02:15:02 | Re: Batching in executor |
Previous Message | Yugo Nagata | 2025-09-30 02:01:58 | Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION |