-
Notifications
You must be signed in to change notification settings - Fork 205
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
Add documentation for upgrading PostgreSQL database #4171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation of my suggested changes: #4193
`/etc/sysconfig/postgresql` and should be `/var/lib/pgsql/data` by default. The | ||
paths in the next steps assume the default. | ||
|
||
2. To ease migrations, I would recommend making the `data`-directory a symlink |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Who is the I here? I suggest to write instead s/I would recommend/it is recommended/
+ | ||
[source,sh] | ||
---- | ||
martchus@ariel:~> sudo -u postgres ls -l /var/lib/pgsql | grep data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be non-personalized
This commit moves the database migration section to the advanced chapter to keep the basic installation simpler for new users. Existing and advanced users might need to follow a database version migration but there are also use cases of fresh reinstalls if the test results in the database are not worth to keep or container setups with externally maintained databases. This is a follow-up to commit 413abd4, #4171 which introduced the section about database migration.
This commit moves the database migration section to the advanced chapter to keep the basic installation simpler for new users. Existing and advanced users might need to follow a database version migration but there are also use cases of fresh reinstalls if the test results in the database are not worth to keep or container setups with externally maintained databases. This is a follow-up to commit 413abd4, os-autoinst#4171 which introduced the section about database migration.
See https://progress.opensuse.org/issues/76924#note-10