| From: | Jingtang Zhang <mrdrivingduck(at)gmail(dot)com> |
|---|---|
| To: | Yuhang Qiu <iamqyh(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Use maintenance_io_concurrency for parallel index builds |
| Date: | 2026-10-28 16:44:11 |
| Message-ID: | CAPsk3_ASDKa-3fhMTeXqPoa+EV35S26_+P7uXN_75F_jcbzu0A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
I found another maintenance path using effective_io_concurrency:
the sequential heap scan in heapam_relation_copy_for_cluster().
This affects VACUUM FULL and the sequential scan paths of CLUSTER
and REPACK.
Attached is v4, which also passes SO_MAINTENANCE for this scan.
---
Regards,
Jingtang Zhang
| Attachment | Content-Type | Size |
|---|---|---|
| v4-index-maintenance-io.patch | application/octet-stream | 5.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2026-10-28 17:22:47 | Re: Parallel vacuum: check XID wraparound failsafe between indexes |
| Previous Message | Andres Freund | 2026-10-28 16:42:49 | Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e |