Re: Why does PostgresNode.pm set such a low value of max_wal_senders? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Why does PostgresNode.pm set such a low value of max_wal_senders?
Date
Msg-id 20200929224448.GA15427@alvherre.pgsql
Whole thread Raw
In response to Why does PostgresNode.pm set such a low value of max_wal_senders?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why does PostgresNode.pm set such a low value of max_wal_senders?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-Sep-29, Tom Lane wrote:

> So I wonder why PostgresNode.pm is doing
> 
>         print $conf "max_wal_senders = 5\n";
> 
> Considering that our default these days is 10 senders, and that a
> walsender slot doesn't really cost much, this seems unduly cheapskate.
> I propose raising this to 10.

I suggest to remove that line.  max_wal_senders used to default to 0
when PostgresNode was touched to have this line in commit 89ac7004dad;
the global default was raised in f6d6d2920d2c.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Why does PostgresNode.pm set such a low value of max_wal_senders?
Next
From: Tom Lane
Date:
Subject: Re: Why does PostgresNode.pm set such a low value of max_wal_senders?