| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | lejeczek <peljasz(at)yahoo(dot)co(dot)uk>, "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:49:48 |
| Message-ID: | 2feeb2ea2d0c6164309fefa316d44442047e1db6.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lejeczek | 2024-01-26 15:21:19 | Re: max_wal_senders - stuck on |
| Previous Message | David G. Johnston | 2024-01-26 14:24:03 | Re: max_wal_senders - stuck on |