Re: Finalizing read stream users' flag choices - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Finalizing read stream users' flag choices
Date
Msg-id CA+TgmoYm14mCPvinc8DCs7_aUR1M1NPmQpWND=r_j8ysaMLv6Q@mail.gmail.com
Whole thread Raw
In response to Finalizing read stream users' flag choices  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Tue, Apr 8, 2025 at 12:07 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> We've said before that maintenance_io_concurrency should govern work
> done on behalf of many different sessions. That was said to include at
> least vacuum and recovery. I need to change the index vacuum users to
> use READ_STREAM_MAINTENANCE. But I wonder about the other users like
> amcheck and autoprewarm.

autoprewarm, and possibly regular prewarm, seem like maintenance to
me. amcheck does not.

Otherwise, the choices you've made about what is maintenance seem
reasonable to me, based on the list you included further down in the
email.

I don't know enough to opine on the questions about full vs. default,
or sequential scans.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Wolfgang Walther
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Next
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER