diff options
| author | 2025-11-17 00:27:24 +0100 | |
|---|---|---|
| committer | 2025-11-17 00:27:24 +0100 | |
| commit | 9c8e9a8b874b50f63c061390ff817518965b0a88 (patch) | |
| tree | 45a9c5ac848c6a458c475d39435f800e6c8ee4a5 /app/Models/EntryDAO.php | |
| parent | b9abe706902c666d85cf60eb828a72c4f3062297 (diff) | |
Fix Docker for PostgreSQL (#8224)
Better fix instead of https://github.com/FreshRSS/FreshRSS/pull/8216
Based on error message:
Error: in 18+, these Docker images are configured to store database data in a
format which is compatible with "pg_ctlcluster" (specifically, using
major-version-specific directory names). This better reflects how
PostgreSQL itself works, and how upgrades are to be performed.
See also https://github.com/docker-library/postgres/pull/1259
Counter to that, there appears to be PostgreSQL data in:
/var/lib/postgresql/data (unused mount/volume)
This is usually the result of upgrading the Docker image without
upgrading the underlying database using "pg_upgrade" (which requires both
versions).
The suggested container configuration for 18+ is to place a single mount
at /var/lib/postgresql which will then place PostgreSQL data in a
subdirectory, allowing usage of "pg_upgrade --link" without mount point
boundary issues.
See https://github.com/docker-library/postgres/issues/37 for a (long)
discussion around this process, and suggestions for how to do so.
Diffstat (limited to 'app/Models/EntryDAO.php')
0 files changed, 0 insertions, 0 deletions
