>> This is a rather awkward position for upgraders to be in, as we >> essentially cannot automate this robustly.
Is it really that much of a problem to do something like: su -s /bin/sh -c 'pg_dumpall -c' - postgres >/var/tmp/old_pg94.sql pg_dropcluster 9.4 main --stop ... pg_createcluster 9.4 main service postgres start su -s /bin/sh -c 'psql -f /var/tmp/old_pg94.sql template1' - postgres after checking the size of the data directory vs the amount of free disk space, what 9.4 clusters exist, which ports they each use, et cetera, with the upgrade occuring at the ... point? And stop like it currently did if there isn't enough space. I didn't move anything big over to 9.4, just some small stuff I knew I could afford to deal with should a dump/restore be required, but I still had to fuss with one or two of them to get the pattern down. And for one server I even managed to get β3 installed before grabbing a fresh dump from β2, and had to resort to using an old dump (but not so old that I lost anything). I can imagine that it could be quite an ordeal for some users. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
