got collation warning after pull of latest postgres:17
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, postgres
- Domain
- databases, documentation
Research direction
Start by reviewing the postgres Docker Official Image page at https://hub.docker.com/_/postgres and compare the postgres:17 and postgres:17-bookworm image notes. Confirm whether the Debian base-image change causes the collation warning, then document the warning and the affected persisted-database scenario on the main image page.
Written by the indexing model from the issue text.
Description
I was using for some persisted test database postgres:17 image
After the most recent pull of the image and restart, I got for a persisted db:
DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
I assume this is due to postgres:17 moved to using debian trixi, as after restarting with image postgres:17-bookworm no more warnings are displayed.
(hostsystem is bullseye, maybe also related)
I do know that latest images are almost always not a good idea, but somehow I always associated this to the main application, not an underlying change of os system used in a Dockerfile.
But ok, my bad.
I only reported this so others are aware. If confirmed, and not my error, then maybe a warning on the main info page on https://hub.docker.com/_/postgres will help others.
- Dominant language
- Shell
- Stars
- 2.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker-library/postgres
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
docker-library/postgres#1420 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
docker-library/postgres#1419 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
docker-library/postgres#1389 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
docker-library/postgres#1355 · 10 comments · 11 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
docker-library/postgres#1349 · 3 comments ·
All issues in docker-library/postgres
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppImage/appimage.github.io#9676 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
YunoHost-Apps/pixelfed_ynh#346 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ChrisTitusTech/dwm-titus#367 ·
Maintainers usually reply within 1 day