Gregory Youngblood wrote: > 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.
Based on the discussion on this matter, it seems obvious that we want to do a parallel install, and make people switch that way, in their own pace. The only real problem with parallel installs is the naming. We cannot rename the current postgresql without rpm treating it as an Erase-Install situation, and configuration files will end up as .rpmsave etc. So the new package will have to be named something like postgresql81, which I detest, since it messes with our upgrade options later on. Of course, if we decide on a separate naming scheme for postgresql and other packages that needs the same kind of treatment, we could do that. I don't like the idea of detecting .rpmsave files and copying them back etc, so that's not really an option. We have time to figure this out though. :) If anyone wants to start on a newer postgresql package for contrib, I suggest calling it something like postgresql-8.1 or similar, so that we can merge it into mainline later on. Kind regards c -- Christian Haugan Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
