Scooby Husky a1d6091122 Fix VPS replica clusters: match home's max_connections (recovery abort) ...

Postgres refuses to replay WAL past a checkpoint recorded with higher
max_connections/max_wal_senders/etc than the recovering instance's own
settings: 'recovery aborted because of insufficient parameter settings:
max_connections = 100 is a lower setting than on the primary server,
where its value was 200' - confirmed live on all 3 VPS clusters (they
had no postgresql.parameters block at all, defaulting to CNPG's 100).
Copied home's full postgresql.parameters block to remove any other
potential mismatch (max_wal_senders, max_worker_processes are subject
to the same check). Bumped memory requests/limits to match home too -
shared_buffers: 512MB needs headroom the previous 256Mi/1Gi didn't have.

2026-08-17 23:15:02 -05:00

..

manifests

Fix VPS replica clusters: match home's max_connections (recovery abort)

2026-08-17 23:15:02 -05:00

values.yaml

…