Обсуждение: max_wal_senders - stuck on
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.
thanks, L.
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.
thanks, L.
On Friday, January 26, 2024, lejeczek <peljasz@yahoo.co.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.
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, whereits 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
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, whereits 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.
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/