-
Notifications
You must be signed in to change notification settings - Fork 35
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.
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
Postgresql13 support #43
Comments
Hi, I can look into it, but I don't have any system with OmniPITR now. Is there specific problem that you're seeing? |
The configuration between 9.3 and 13 is different. I was able to configure the replication with the script omnipitr-synch, the standby server doesnt know about the replication slot, even the manual creation doesnt work. It works only if pg_basebackup is used, which creates a configuration file for recovery. After that, the omnipitr-restore starts to work correctly and then the switch to synchronous replication. Is it possible to add a support for 13, to do not have the above workarounds. |
So, I'm not sure what would be the correct fix. The thing is that recovery.conf is gone, and instead one should put the values in postgresql.conf. Modification of postgresql.conf by omnipitr are unlikely to happen, for many reasons. Will think some more on it, and let you know what I will decide. It will not happen soon, though. Sorry. |
I tried to debug the problem, but I think my knowledge of omnipitr got a bit rusty due to years of not using it. Can you please write me:
|
Hi Depesz,
It's possible to add a support for a new postgresql-13 for omnipitr?
The text was updated successfully, but these errors were encountered: