Add maintenance_io_concurrency flag to some read stream users
authorMelanie Plageman
Mon, 28 Apr 2025 18:19:45 +0000 (14:19 -0400)
committerMelanie Plageman
Mon, 28 Apr 2025 18:19:45 +0000 (14:19 -0400)
commitf132815fd717f26613dcc3888608044eac91a7ac
treebdd9a94e7a04c1e738e2ae27b8c21cf470dc2cf4
parentce72e7e02e1c9075f8dd492f55281398d0721eb8
Add maintenance_io_concurrency flag to some read stream users

Index vacuuming and [auto]prewarm AIO concurrency should be governed by
maintenance_io_concurrency. As such, pass those read stream users the
READ_STREAM_MAINTENANCE flag which will calculate their read stream
distance with maintenance_io_concurrency instead of
effective_io_concurrency. This was an oversight in the original commits
making those operations use the read stream API.

Discussion: https://postgr.es/m/flat/CAAKRu_aopDxTo4b41Mt_7Zc-z0_ngocrY8SFCCY6Aph1HgwuNw%40mail.gmail.com
contrib/pg_prewarm/autoprewarm.c
contrib/pg_prewarm/pg_prewarm.c
src/backend/access/gist/gistvacuum.c
src/backend/access/nbtree/nbtree.c
src/backend/access/spgist/spgvacuum.c