Ross ROSS = Recommend OSS · open-source software intelligence for agents

pgautoupgrade/docker-pgautoupgrade

A PostgreSQL Docker container that automatically upgrades your database observed · 2026-09-03

github.com/pgautoupgrade/docker-pgautoupgrade · homepage · Shell · MIT (permissive) observed · 2026-09-03

Health v2 · maintenance only

74/100

  • Activity 100
  • Release rhythm 35
  • Longevity 82

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1152
  • days_rel: n/a
  • days_push: 0
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1184 stars · 32 forks observed · 2026-09-03

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A PostgreSQL Docker image that automatically detects the version of an existing database data directory and upgrades it in place using pg_upgrade before starting the server. It supports PostgreSQL 9.5 through the latest versions, with Alpine and Debian-based image variants and an optional one-shot upgrade mode.

Use cases

  • automatically upgrade postgresql docker container to a new major version
  • upgrade postgres data directory without manual pg_upgrade steps
  • replace official postgres docker image with one that handles version upgrades
  • run a one-shot in-place postgres upgrade in docker
  • migrate postgres 9.5+ database files to postgres 17 or 18 in a container
  • avoid manual dump and restore when upgrading postgresql in docker

When to choose

  • you run PostgreSQL in Docker and want seamless major version upgrades on container start
  • you want to avoid manual pg_upgrade or dump/restore procedures
  • you need both Alpine and Debian-based image options to match your existing setup
  • you want a one-shot upgrade without keeping the server running

When to avoid

  • you need guaranteed safety without backups - in-place upgrades can fail and destroy data
  • you rely on custom healthchecks that are incompatible with this image
  • you are not using Docker or containerized PostgreSQL
  • you need to upgrade across unsupported version gaps or non-standard data directory layouts

Facets

application · maturity active

database deployment developer-tools databases self-hosted self-hosted postgresql pg-upgrade docker-image database-migration version-upgrade devops containers docker linux

5 sources

Member repositories

RepositoryRoleHealth v2
pgautoupgrade/docker-pgautoupgrademain74

For agents

markdown · JSON · MCP: product_card(name="pgautoupgrade/docker-pgautoupgrade")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem