Feedback-ID: ia2694551:Fastmail
Date: Fri, 26 Jan 2024 16:38:00 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: lejeczek <peljasz@yahoo.co.uk>
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: max_wal_senders - stuck on
Message-ID: <202401261538.xkont4a7sdpt@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5a0b25d3-8d8c-4bc8-88f0-4f105737ee6e@yahoo.co.uk>
Archived-At: 
 <https://www.postgresql.org/message-id/202401261538.xkont4a7sdpt%40alvherre.pgsql>
Precedence: bulk

On 2024-Jan-26, lejeczek wrote:

> On 26/01/2024 15:49, Laurenz Albe wrote:
> > On Fri, 2024-01-26 at 15:17 +0100, lejeczek wrote:

> > >   2024-01-26 15:13:14.315 CET [1279777] DETAIL:  max_wal_senders = 10 is a lower setting than on the primary server, where its value was 48.
> > > 
> > >   and I've checked config files (I'm on Ubuntu with pgSQL 14.10) - no _max_wal_senders_ set there.
> >
> > Perhaps max_wal_senders was 48 earlier, and that value is logged in the WAL?
>
> Yes, earlier it was, now removed - 10 is the default I guess - how to "fix"
> this? (possibly without _pg_base..._)

Change the postgresql.conf config file in the replica to say
max_wal_senders=48 and start it.  (You may have postgresql.auto.conf or
other files with the setting, which you'll have to remove or comment out).

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/