PostgreSQL 17 • Hacker News Board

Re: PostgreSQL 17

#151

Post by justinclift » Tue, Oct 01, 2024, 5:26 AM UTC

ktosobcy wrote: post #123

ellisv wrote: post #28

Earlier quoted context omitted.

I'm curious what you feel is specifically missing.

Being able to simply switch from "postgres:15" to "postgres:16" in docker for example (I'm aware about pg_autoupdate but it's external and I'm a bit iffy about using it) What's more, even outside of docker running `pg_upgrade` requires both version to be present (or having older binary handy). Honestly, having the previous version logic to load and process the database seems like it would be little hassle but would i…

> I'm a bit iffy about using it

It's not perfect, as it doesn't (yet) recreate indexes or automatically run `vacuum analyze` afterwards. We're working on those though. :)

You do make backups of your database though yeah?

Re: PostgreSQL 17

#152

Post by ktosobcy » Wed, Oct 02, 2024, 3:37 PM UTC

justinclift wrote: post #151

ktosobcy wrote: post #123

Earlier quoted context omitted.

Being able to simply switch from "postgres:15" to "postgres:16" in docker for example (I'm aware about pg_autoupdate but it's external and I'm a bit iffy about using it) What's more, even outside of docker running `pg_upgrade` requires both version to be present (or having older binary handy). Honestly, having the previous version logic to load and process the database seems like it would be little hassle but would i…

> I'm a bit iffy about using it It's not perfect, as it doesn't (yet) recreate indexes or automatically run `vacuum analyze` afterwards. We're working on those though. :) You do make backups of your database though yeah?

Yes I do, but for the simplicy I just stick with the same PG version and doesn't touch it once deployed on local RPi :D

Re: PostgreSQL 17

#153

Post by justinclift » Thu, Oct 03, 2024, 12:36 AM UTC

ktosobcy wrote: post #152

justinclift wrote: post #151

Earlier quoted context omitted.

> I'm a bit iffy about using it It's not perfect, as it doesn't (yet) recreate indexes or automatically run `vacuum analyze` afterwards. We're working on those though. :) You do make backups of your database though yeah?

Yes I do, but for the simplicy I just stick with the same PG version and doesn't touch it once deployed on local RPi :D

Heh Heh Heh. Yeah, that's how most people seem to do it, even on non-docker systems. ;)

Works well for a few years as PG is super stable. But we tend to see people when they've run their systems longer than that and it's gotten to the point of their PG install is end of life (or similar circumstance), so they're looking at their upgrade options.

The pgautoupgrade approach is one potential way to fix that, and (in theory) should mean that once they're using it they don't have to worry about major version upgrades ever again (in a positive way).