🔎 how to migrate postgres 13 db to postgres 17 not scary easy explained for kids please don't fuck anything up one liner terminal linux
-
how to migrate postgres 13 db to postgres 17 not scary easy explained for kids please don't fuck anything up one liner terminal linux -
how to migrate postgres 13 db to postgres 17 not scary easy explained for kids please don't fuck anything up one liner terminal linux
@MagicLike have a backup and dont do it for the first time on production
-
@MagicLike have a backup and dont do it for the first time on production
@mayu well I mean I will stop every service and run a backup through hetzner and dump the db to a local backup I think that will be enough but tbh I am doing this for the first time and I have no idea where to start
-
how to migrate postgres 13 db to postgres 17 not scary easy explained for kids please don't fuck anything up one liner terminal linux
Seriously can anyone give me a hint where to look?
-
Seriously can anyone give me a hint where to look?
So what I ended up doing was purging the postgres 16 & 17 installs and doing a fresh new install of postgres 17. This triggered some kind of auto migration tool of postgres and I just needed to say "yes" a few times and it did everything by itself. Now I only need to drop the pg 13 cluster and I am done :3
-
So what I ended up doing was purging the postgres 16 & 17 installs and doing a fresh new install of postgres 17. This triggered some kind of auto migration tool of postgres and I just needed to say "yes" a few times and it did everything by itself. Now I only need to drop the pg 13 cluster and I am done :3
-
So what I ended up doing was purging the postgres 16 & 17 installs and doing a fresh new install of postgres 17. This triggered some kind of auto migration tool of postgres and I just needed to say "yes" a few times and it did everything by itself. Now I only need to drop the pg 13 cluster and I am done :3
@MagicLike I think this is what it can do in Debian, nice.
My approach is to stop everything else, use pg_dump on the old version, then psql to load it into the new version (which has distinct Docker volumes). That works with Docker images that aren't designed for upgrades. Except that I'm still using an old version as I haven't debugged some potential authentication changes.
-
@MagicLike I think this is what it can do in Debian, nice.
My approach is to stop everything else, use pg_dump on the old version, then psql to load it into the new version (which has distinct Docker volumes). That works with Docker images that aren't designed for upgrades. Except that I'm still using an old version as I haven't debugged some potential authentication changes.
@lukyan mhm I mean I dumped the cluster anyway beforehand just to be sure but wanted it to actually migrate cleanly before doing it all manually - but yeah I don't really like Docker so I opted to do everything bare-metal and it has been a smooth sailing for me so far...
