{
  "id": 20913603,
  "title": "How to Upgrade to PostgreSQL 19: postgres:latest Won't Start on Your Old Volume",
  "url": "https://urgent.news/2026/11/20/how-to-upgrade-to-postgresql-19-postgres-latest-wont-start-on-your",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-20T15:10:01.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/alanwest/how-to-upgrade-to-postgresql-19-postgreslatest-wont-start-on-your-old-volume-36id"
  },
  "original_language": "en",
  "account": "Docker Hub now offers the PostgreSQL 19 image under the tag \"latest\", replacing the previous \"postgres:latest\" tag. This new image stores database data in a format incompatible with older PostgreSQL versions (17 or 18). As a result, when you attempt to start your database using the \"postgres:latest\" tag, the entrypoint will encounter an error stating that the data format is incompatible with version 19 and terminate the process. Your data remains intact, but the database will be unavailable until you take steps to upgrade it or stick with the older version.",
  "summary": "If your compose file says image: postgres:latest , then as of November 20 it says PostgreSQL 19. The Docker Hub tag list now has 19.0 , 19 and latest on the same line. The image keeps its data under a version-numbered path ( /var/lib/postgresql/19/docker ), so after the next docker compose pull && docker compose up -d the entrypoint finds your 17 or 18 data somewhere else, prints Error: in 18+,…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}