Re: Why does PostgresNode.pm set such a low value of max_wal_senders?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why does PostgresNode.pm set such a low value of max_wal_senders?
Date: 2020-09-30 07:22:52
Message-ID: 20200930072252.GN1996@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 29, 2020 at 07:04:22PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> 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.
>
> Hm. We could do so back to v10 where that came in, and there are no
> src/test/subscription tests before v10, so that should be sufficient.
> Sold.

+1.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-09-30 07:27:46 Re: Change a constraint's index - ALTER TABLE ... ALTER CONSTRAINT ... USING INDEX ...
Previous Message Michael Paquier 2020-09-30 07:17:50 Re: Add timeline to partial WAL segments