3 ms·

This is a very confusing title and project at first glance. It took me a minute to figure out what you’re doing… But just to be clear — the point of this is to

This is a very confusing title and project at first glance. It took me a minute to figure out what you’re doing… But just to be clear — the point of this is to migrate an existing Postgres DB from the original version to a newer version? This is about the data volume itself, not automatically upgrading the Postgres binary when a new version is released? So, you’d basically pass a flag that says --migrate-db when starting the container to kick start changing the data on disk? So when you start a new Postgres 15 container, you could pass it a volume with Postgres 13 data and it would auto update the on disk DB data.

justinclift 3y ago
It's pretty much answered here: https://news.ycombinator.com/item?id=36747498 https://news.ycombinator.com/item?id=36747498 The upgrade-of-your-data happens automatically when the container starts, prior to starting the database server.
- mbreese 3y ago
  Right, but you’re not actually automatically migrating a Postgres 13 program to Postgres 15 in a running container. That was what I first thought when I read the title. You’re using the work “upgrade” differently than how I normally think about it when talking about version changes. You’re talking about data-on-disk, not just the program version. (I realize that when talking about Postgres, the two are linked, but that’s not the case for most programs)
  - justinclift 3y ago
    Is there better wording that's concise? I'm just going with what I thought of, but am happy to adjust things as makes sense. :)
    - deleted 3y ago
      [deleted]
    - rcfox 3y ago
      "A PostgreSQL Docker container that automatically upgrades your database" Still uses "upgrade", but highlights the fact that you're changing the artifact and not just the software.
      - justinclift 3y ago
        Thanks, that sounds good. Looks like I can't edit the title for this any more now though. I'll email the HN mods and ask them if they can do it. :)
        justinclift 3y ago
        Title changed. :) Also copied that wording to the GitHub repo page, Docker Hub page, and will probably use it everywhere else that needs a description too. :D
Izkata 3y ago
Postgres docs do use the word upgrade, for example: > pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore typically required for major version upgrades https://www.postgresql.org/docs/current/pgupgrade.html https://www.postgresql.org/docs/current/pgupgrade.html

justinclift 3y ago

It's pretty much answered here: https://news.ycombinator.com/item?id=36747498 https://news.ycombinator.com/item?id=36747498 The upgrade-of-your-data happens automatically when the container starts, prior to starting the database server.

mbreese 3y ago
Right, but you’re not actually automatically migrating a Postgres 13 program to Postgres 15 in a running container. That was what I first thought when I read the title. You’re using the work “upgrade” differently than how I normally think about it when talking about version changes. You’re talking about data-on-disk, not just the program version. (I realize that when talking about Postgres, the two are linked, but that’s not the case for most programs)
- justinclift 3y ago
  Is there better wording that's concise? I'm just going with what I thought of, but am happy to adjust things as makes sense. :)
  - deleted 3y ago
    [deleted]
  - rcfox 3y ago
    "A PostgreSQL Docker container that automatically upgrades your database" Still uses "upgrade", but highlights the fact that you're changing the artifact and not just the software.
    - justinclift 3y ago
      Thanks, that sounds good. Looks like I can't edit the title for this any more now though. I'll email the HN mods and ask them if they can do it. :)
      - justinclift 3y ago
        Title changed. :) Also copied that wording to the GitHub repo page, Docker Hub page, and will probably use it everywhere else that needs a description too. :D

Izkata 3y ago

Postgres docs do use the word upgrade, for example: > pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore typically required for major version upgrades https://www.postgresql.org/docs/current/pgupgrade.html https://www.postgresql.org/docs/current/pgupgrade.html