Jan Nieuwenhuizen writes: > Roel Janssen writes: > >> So, it would be something like: >> postgres pg_upgrade \ >> ... > > It's great to have a recipe `that works', so thanks! > > However, whether or not we automate this, I cannot help to wonder if > we should support downgrading -- at least to the previous version > in this case? > > If I'm not mistaken, everything else in GuixSD will run if I select a > previous system generation in Grub...except for this? > > Is involving postgres developers an option, I'm sure a least one of > the postgresql hackers[cc] are already looking at Guix[SD]? > > Greetings, > janneke
Ah yes, I see the point. The problem here is that when new features are added to PostgreSQL, and you rely upon them in your database schemas, downgrading will most likely cause loss of information. Maybe we need a wrapper script that also makes a dump of all of the data? Now that could become a security hole. Or the wrapper script warns about this situation, and recommends making a (extra) back-up of the database before upgrading. Or.. the upgrade is something a user should do explicitly, basically giving up on the "just works" concept. Guix already provides a nice way to get the previous version of the exact binaries used before the upgrade. Kind regards, Roel Janssen -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
