Skip to content

Commit

Permalink
Update PostgreSQL update instructions for 17.0
Browse files Browse the repository at this point in the history
Update PostgreSQL update instructions for 17.0
  • Loading branch information
androidnisse committed Oct 4, 2024
1 parent dc2b39f commit d1f76ed
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/user/software/development/postgresql.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,15 +31,15 @@ sudo -u postgres psql

Note that all local connections are trusted and can access all databases by default. This can be changed in `/var/db/pgsql/data/pg_hba.conf`, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html) for more details.

## Updating to 16
## Updating to 17

Because PostgreSQL is included as a single package, the only way to perform a major upgrade of PostgreSQL is via a backup/restore. The procedure below describes the upgrade process as it applies to Solus. See the [PostgreSQL documentation](https://www.postgresql.org/docs/16/upgrading.html#UPGRADING-VIA-PGDUMPALL) for more details.
Because PostgreSQL is included as a single package, the only way to perform a major upgrade of PostgreSQL is via a backup/restore. The procedure below describes the upgrade process as it applies to Solus. See the [PostgreSQL documentation](https://www.postgresql.org/docs/17/upgrading.html#UPGRADING-VIA-PGDUMPALL) for more details.

1. If you have already updated PostgreSQL, downgrade PostgreSQL back to 15.4:
1. If you have already updated PostgreSQL, downgrade PostgreSQL back to 16.4:

```bash
sudo eopkg it https://cdn.getsol.us/repo/shannon/p/postgresql/postgresql-15.4-42-1-x86_64.eopkg \
https://cdn.getsol.us/repo/shannon/p/postgresql/postgresql-libpq-15.4-42-1-x86_64.eopkg
sudo eopkg it https://cdn.getsol.us/repo/shannon/p/postgresql/postgresql-16.4-51-1-x86_64.eopkg \
https://cdn.getsol.us/repo/shannon/p/postgresql/postgresql-libpq-16.4-51-1-x86_64.eopkg
```

2. (Re)start PostgreSQL:
Expand Down

0 comments on commit d1f76ed

Please sign in to comment.