Opened 3 years ago
Closed 3 years ago
#15631 closed enhancement (fixed)
postgresql-14.0
| Reported by: | Douglas R. Reno | Owned by: | thomas |
|---|---|---|---|
| Priority: | normal | Milestone: | 11.1 |
| Component: | BOOK | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
New major version
Change History (4)
comment:1 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
follow-up: 3 comment:2 by , 3 years ago
It looks like anyone that uses this will need to run a pg_upgrade prior to restarting postgresql.
comment:3 by , 3 years ago
Replying to Douglas R. Reno:
It looks like anyone that uses this will need to run a pg_upgrade prior to restarting postgresql.
which is, afaik, recommended on every major version change anyhow. Our current instructions are very basic in this regard. To me, it looks like the easiest way to support surviving a format change of the DB is when we do not merge postgres to /usr but install it in /opt/postgresql-x.y.z (and have a symlink /opt/postgresql to it used in $PATH). When installing the new version of postgres, the two versions are available on system and after having run the pg_upgrade and everything works, the previous version in /opt can be removed and the symlink changed to the new version.
Same for /srv/pgsql/data which than should be /srv/pgsql/data-x.y.z.
comment:4 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed in [2ed707f] - at least the upgrade
Will open a new ticket to discuss the way to go in regards to upgrading an existing installation.
https://www.postgresql.org/docs/release/14.0/