[PATCH] Use maintenance_io_concurrency for parallel index builds

From: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: 邱宇航 <iamqyh(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: [PATCH] Use maintenance_io_concurrency for parallel index builds
Date: 2026-09-08 16:12:25
Message-ID: CAPsk3_BaXgiA3c=GR63kU6O478MWggYtBCx3vWnW6d87F3=0nA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Parallel B-tree, GIN, and BRIN index builds currently use
effective_io_concurrency for heap scans because the scans do not
pass READ_STREAM_MAINTENANCE to the read stream.

The attached patch passes the maintenance context through the existing
scan flags, making these scans use maintenance_io_concurrency.

Serial index builds appear to have the same issue. Passing the flag
there seems to require extending the table scan interface, which
could be follow-up work.

---
Regards,
Jingtang Zhang

Attachment Content-Type Size
v1-parallel-index-maintenance-io.patch application/octet-stream 3.1 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-09-08 16:16:36 Re: Improve error handling in test modules: test_extensible, test_bitmapset
Previous Message Greg Burd 2026-09-08 15:58:42 Re: Speed up COPY FROM text/CSV parsing using SIMD