aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorMelanie Plageman <melanieplageman@gmail.com>2025-04-28 14:19:45 -0400
committerMelanie Plageman <melanieplageman@gmail.com>2025-04-28 14:19:45 -0400
commitf132815fd717f26613dcc3888608044eac91a7ac (patch)
treebdd9a94e7a04c1e738e2ae27b8c21cf470dc2cf4 /src/backend/access/gist/gistvacuum.c
parentce72e7e02e1c9075f8dd492f55281398d0721eb8 (diff)
downloadpostgresql-f132815fd717f26613dcc3888608044eac91a7ac.tar.gz
postgresql-f132815fd717f26613dcc3888608044eac91a7ac.zip
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
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
-rw-r--r--src/backend/access/gist/gistvacuum.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/access/gist/gistvacuum.c b/src/backend/access/gist/gistvacuum.c
index 6a359c98c60..dca236b6e57 100644
--- a/src/backend/access/gist/gistvacuum.c
+++ b/src/backend/access/gist/gistvacuum.c
@@ -215,7 +215,8 @@ gistvacuumscan(IndexVacuumInfo *info, IndexBulkDeleteResult *stats,
* It is safe to use batchmode as block_range_read_stream_cb takes no
* locks.
*/
- stream = read_stream_begin_relation(READ_STREAM_FULL |
+ stream = read_stream_begin_relation(READ_STREAM_MAINTENANCE |
+ READ_STREAM_FULL |
READ_STREAM_USE_BATCHING,
info->strategy,
rel,