New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PITR fails if max_connections has been increased #255

Open

benwaffle opened this issue Aug 12, 2024 · 0 comments

Labels

bug

Contributor

benwaffle commented Aug 12, 2024

Create a db
Run fly pg config update --max-connections 320
Enable backups with fly pg backups enable
Restore from backup with fly pg backups restore new-db
The new DB fails to become healthy, and I don't think postgres ever exits recovery mode:

2024-08-12T19:55:42Z app[3d8dd719a93e78] iad [info]postgres | 2024-08-12 19:55:42.084 UTC [393] FATAL:  recovery aborted because of insufficient parameter settings
2024-08-12T19:55:42Z app[3d8dd719a93e78] iad [info]postgres | 2024-08-12 19:55:42.084 UTC [393] DETAIL:  max_connections = 300 is a lower setting than on the primary server, where its value was 320.

The text was updated successfully, but these errors were encountered:

benwaffle mentioned this issue

PITR fails due to wrong postgres password #256

Open

benwaffle added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment