You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today on our Ubuntu-based cluster, we installed updates via apt and our cluster broke.
Logs on the monitor node said
Dec 06 10:19:07 monitor01 pg_autoctl[67687]: 10:19:07 67687 ERROR Error 22023 while running Postgres query: ALTER EXTENSION "pgautofailover" UPDATE TO "2.1":
Dec 06 10:19:07 monitor01 pg_autoctl[67687]: 10:19:07 67687 ERROR ERROR: extension "pgautofailover" has no update path from version "2.0" to version "2.1"
A bit of research told me that postgresql extension updates require an sql file with the filename <extension>--<old version>--<new version>.sql.
@DimCitus Firstly, I hasten to thank you for your work!
I ask you to add the pgautofailover--2.0--2.1.sql file to the current issue, since errors are made without it when installing the expansion. @Akkowicz released PullRequest - #1019
Thank you again a lot!
Today on our Ubuntu-based cluster, we installed updates via apt and our cluster broke.
Logs on the monitor node said
A bit of research told me that postgresql extension updates require an sql file with the filename
<extension>--<old version>--<new version>.sql
.I've looked in the repo and found them here, but a file for 2.0 to 2.1 is indeed missing. Instead there's "2.0 to dummy" at https://github.com/hapostgres/pg_auto_failover/blob/main/src/monitor/pgautofailover--2.1--dummy.sql.
I've looked at the update sql file for 1.6 to 2.0 which didn't contain anything except comments, so I've copied it and named it appropriately:
Now the cluster was able to start again. I just don't know if the actual upgrade file would have had important instructions that we have not applied.
The text was updated successfully, but these errors were encountered: