PostgreSQL runtime.conf not updating properly during PG13 HA upgrades
When updating an existing HA cluster to PostgreSQL 13, there is a problem where PostgreSQL will not restart.
For context on the diagnostics, see the upgrading steps validation discussion thread.
What @pursultani and I discovered is that the runtime.conf
is not being copied over, leaving Patroni with the proper PG13 runtime configuration file usingwal_keep_size
while Postgres still had wal_keep_segments
from PG12. Due to this, when Postgres tried to start up - it failed because the runtime configuration had this deprecated field.