doc:appunti:linux:sa:postgresql_upgrade
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:appunti:linux:sa:postgresql_upgrade [2020/03/02 17:45] – [Upgrade strategy] niccolo | doc:appunti:linux:sa:postgresql_upgrade [2020/03/02 17:48] – [Upgrade cluster from 9.6 to 11] niccolo | ||
---|---|---|---|
Line 56: | Line 56: | ||
</ | </ | ||
- | now we can DROP them: | + | Then we DROP them: |
< | < | ||
Line 66: | Line 66: | ||
===== Upgrade cluster from 9.6 to 11 ===== | ===== Upgrade cluster from 9.6 to 11 ===== | ||
- | Drop the new 11 main cluster (which should be empty, actually): | + | Drop the new 11/main cluster (which should be indeed |
< | < | ||
Line 82: | Line 82: | ||
< | < | ||
Fixing hardcoded library paths for stored procedures... | Fixing hardcoded library paths for stored procedures... | ||
- | Upgrading database | + | Upgrading database |
- | Analyzing database | + | Analyzing database |
</ | </ | ||
- | Verify the new situation. Notice that the new 11 cluster was moved to the default **TCP** port **5432**: | + | Verify the new situation. Notice that the new **11/ |
< | < | ||
Line 101: | Line 101: | ||
</ | </ | ||
- | Now the **11 main cluster** is running, but **started by the postgres user**. We want it to be started by the regular **systemd** subsystem. To fix the situation run the following as the postgres user: | + | Now the **11/main cluster** is running, but **started by the postgres user**. We want it to be started by the regular **systemd** subsystem. To fix the situation run the following as the postgres user: |
< | < |
doc/appunti/linux/sa/postgresql_upgrade.txt · Last modified: 2022/07/07 10:53 by niccolo