On Wed, 2006-03-29 at 13:16 +0100, Andy Shellam wrote:
> This is true, but you could run the new version on the same server/different
> port to the current version, and do a simultaneous dump/restore without
> having to use extra disk space, or taking your production database offline -
> then you can schedule a time to kill the old one, re-assign the port on the
> new one and bring it up - would take about 30 seconds, and this could be
> done at a time when traffic was at its lowest.
Running the new version on another port in the samme server does not
help much. You have to initialize the new version to use new data
partitions (so you need the double of the disk space you have in
production.
Another minus is that this works only in a 'read only' database, all the
updates from you start the dump/restore process until you
kill/re-assign/start again won't be in the new version (and this can be
a lot of data in a busy/large system)
--
Rafael Martinez, <r.m.guerrero@usit.uio.no>
Center for Information Technology Services
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
