On Tue, 2005-12-13 at 15:57 +0100, Tobias Bußmann wrote: > Morten Nilsen <[EMAIL PROTECTED]> wrote: > > Christian H. Toldnes wrote: > >> We need to figure out a way of doing that transition though, since > >> 3.0 users will be automatically upgraded to 3.1 when it's out. 3.1 is > >> actually just 3.0 with changes that are taking place during 3.0, and > >> some changes to the ISOs etc. > > > > if the manual interaction is as easy as I think it is, doing a simple > > dump in preun, and import in post should do the trick.. > > > > as a bonus, if the install barfs, it would leave a dump in some > > predetermined location for easy recovery.. > > Some thoughts on that: > I would not recommend an automated way to perform a major PostgreSQL > update - whereas a somewhat assisted way would be fine.
Generally I agree here. You have no way of knowing how large of a database someone may be running, or how much space a dump would need. One trick I've often used is to take the output of the dump and pipe it into gzip to compress and write directly to a compressed file. The reverse can be done to load, and you never have to uncompress the file into the file system. Not only the space issue, but if the dump/load takes a long time (I have some databases that can take 8 hours to load, let alone dump) then the box being upgraded will have a huge service outage, which may not be acceptable. I think a parallel install, with instructions on how to migrate data, might be a better way to do things. Then the admin can decide on the best process of migrating data for his/her needs. _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
