| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| 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 15:38:00 |
| Message-ID: | 202401261538.xkont4a7sdpt@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larson, Matthew | 2024-01-26 22:30:14 | Barman database recovery and collation version mismatch |
| Previous Message | lejeczek | 2024-01-26 15:21:19 | Re: max_wal_senders - stuck on |