| From: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Asynchronous MergeAppend |
| Date: | 2026-04-13 15:09:06 |
| Message-ID: | 10c97af0ce34ebdb81708b1c49ed6038@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi.
Looked at it. Overall I agree that when we wait for data from one slot
after node initialization, we can't get data from other slots - they are
already either exhausted, or have already received data which is not
needed for now. So it seems that async machinery on later stages is
useless.
Was a bit surprised that asyncresults field is not used in async merge
append anymore, as we save result directly in ms_slots. However, as we
do it only on initial stage, this seems to be OK.
classify_matching_subplans() comment still refers to ms_valid_subplans.
Will look at it once again tomorrow.
--
Best regards,
Alexander Pyhalov,
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2026-04-13 15:10:17 | Re: DELETE/UPDATE FOR PORTION OF with rule system is not working |
| Previous Message | David Geier | 2026-04-13 15:06:40 | Re: Reduce build times of pg_trgm GIN indexes |