Re: max_wal_senders - stuck on

From: lejeczek <peljasz(at)yahoo(dot)co(dot)uk>
To: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: max_wal_senders - stuck on
Date: 2024-01-26 15:21:19
Message-ID: 5a0b25d3-8d8c-4bc8-88f0-4f105737ee6e@yahoo.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 26/01/2024 15:49, Laurenz Albe wrote:
> On Fri, 2024-01-26 at 15:17 +0100, lejeczek wrote:
>>  I have I think pretty weird situation, my primary says:
>>   -> $ sudo --login -u postgres psql --quiet --port=5435 -x -c 'show max_wal_senders'
>>  -[ RECORD 1 ]---+---
>>  max_wal_senders | 10
>>
>>  and slave when told to start, says:
>>  ....
>>  2024-01-26 15:13:14.315 CET [1279777] FATAL:  recovery aborted because of insufficient parameter settings
>>  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?
>
> Yours,
> Laurenz Albe
Yes, earlier it was, now removed - 10 is the default I guess
- how to "fix" this? (possibly without _pg_base..._)
many thanks, L.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2024-01-26 15:38:00 Re: max_wal_senders - stuck on
Previous Message Laurenz Albe 2024-01-26 14:49:48 Re: max_wal_senders - stuck on