| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow changing autovacuum_max_workers without restarting |
| Date: | 2025-04-29 16:43:10 |
| Message-ID: | aBEBniEzYPUXA-yj@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 29, 2025 at 08:36:48AM +0200, Peter Eisentraut wrote:
> On 28.04.25 16:41, Nathan Bossart wrote:
>> On Mon, Apr 28, 2025 at 09:14:54AM -0400, Tom Lane wrote:
>> > My own proposal given the way it works now is to just print
>> > max_connections and not mention autovacuum_worker_slots at all.
>> > Our choice for max_connections is worth reporting, but I don't
>> > feel that everything derived from it needs to be reported.
>>
>> I'm fine with either of these ideas. If I had to choose one, I'd just
>> remove the autovacuum_worker_slots report for the reasons Tom noted.
>
> Yes, removing the report is also fine by me.
Committed.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-04-29 17:14:45 | Re: Disallow redundant indexes |
| Previous Message | Jacob Champion | 2025-04-29 15:57:28 | Re: What's our minimum supported Python version? |