md improvement

This commit is contained in:
2025-11-16 22:27:51 +01:00
parent 49aee045ba
commit c03aebc605
2 changed files with 8 additions and 8 deletions

View File

@@ -6,7 +6,7 @@ author: Sam Hadow
On my server I self-host nextcloud with a PostgreSQL database and this container image *docker.io/library/nextcloud:fpm-alpine*.
You might encounter a collation version mismatch after upgrading Nextcloud or its base image and see messages like these in your logs:
```
```bash
2025-11-02 18:52:12.631 UTC [3514] WARNING: database "nextcloud" has a collation version mismatch
2025-11-02 18:52:12.631 UTC [3514] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-02 18:52:12.631 UTC [3514] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE nextcloud REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
@@ -26,13 +26,13 @@ You can follow this procedure to fix it:
### 1: Enable maintenance mode
The database must not be accessed during the procedure.
```
```bash
podman exec -u www-data nextcloud-app php occ maintenance:mode --on
```
Replace nextcloud-app with the name of your container. And use docker instead of podman if applicable.
### 2: Rebuild the database indexes and refresh the collation version
```
```bash
podman exec -it nextcloud-db bash
psql -U nextcloud nextcloud
REINDEX DATABASE nextcloud;
@@ -45,7 +45,7 @@ Log in to your nextcloud database and then reindex it, depending on the size of
The second command (`ALTER DATABASE ... REFRESH COLLATION VERSION`) just marks the collation version as current in PostgreSQL metadata and removes the warning.
### 3: Disable maintenance mode
```
```bash
podman exec -u www-data nextcloud-app php occ maintenance:mode --off
```