Re: max_wal_senders - stuck on

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: lejeczek <peljasz(at)yahoo(dot)co(dot)uk>
Cc: "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 14:24:03
Message-ID: CAKFQuwbtPtBT-iFTsig4FznKaoMuqY5u65KV4HsfPKSqoNVANg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Friday, January 26, 2024, lejeczek <peljasz(at)yahoo(dot)co(dot)uk> wrote:

> Hi guys.
>
> 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.
>
> All & any suggestions on what is happening there - much appreciated.
>
>
The server/cluster the secondary is talking to isn’t the same
server/cluster that you ran the psql command against?

David J.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2024-01-26 14:49:48 Re: max_wal_senders - stuck on
Previous Message lejeczek 2024-01-26 14:17:40 max_wal_senders - stuck on