Skip to content
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

Problem upgrading pgsql version to 0.10.1 #1306

Open
3 tasks done
toby63 opened this issue Nov 28, 2024 · 0 comments
Open
3 tasks done

Problem upgrading pgsql version to 0.10.1 #1306

toby63 opened this issue Nov 28, 2024 · 0 comments

Comments

@toby63
Copy link

toby63 commented Nov 28, 2024

Baikal version: 0.10.1

  • I have searched open and closed issues for duplicates
  • I have installed the release zip, not the source code zip
  • I have moved the whole, untouched Specific and config folders to the new installation

Problem:

So this is a little special and I don't expect support, but still I have to ask for help here.

Long story as short as possible:

  • On 22nd of March 2024 I installed Baikal 0.9.5 with the postgres PR (Add PostgreSQL backend #1194) applied to it and made a database with postgres.
  • Everything works fine.
  • Yesterday I wanted to upgrade my install to 0.10.1 with the postgres PR now merged upstream. But it does not work.
  • The first error shown in the upgrade web UI was that the database was unaccessible.
  • I then noticed a difference in the config/baikal.yaml file, where my old file uses pgsql: true while the new general file baikal.yaml.dist seems to use backend: mysql. I tried to adjust that to backend: pgsql and then the upgrade procedere in the web UI succeeded, but the admin page is still unaccessible and calendars can't be synced.
  • Reverting to my backup worked and I can continue using my patched 0.9.5 version

Now I would like to ask for potential solutions or ways towards it.

My theory is that maybe the changes made to the PR after March 2024 and the changes made in #1302 could be the reason for this...
but maybe my (unofficial) upgrade scenario was also simply not considered during development.

More info:
I can provide the exact patch of the postgres PR that I used, as there were changes applied to it (upstream) after March 2024 and before it was merged into the main repo.

@leso-kn @ByteHamster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant