3 ms·
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 th
by 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 agoIs 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 agoThanks, 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 agoTitle 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