Rod K wrote: > Paul J Stevens wrote: > >> 1. install 2.2 on hostB while keeping 2.0 up and running on hostA, >> Both connect to the same DBMS instance. >> 2. add the new tables (don't do the BYTEA conversion yet) >> 3. run dbmail-util -by on hostB so the new tables are filled. >> 4. run the BYTEA conversion on the messageblks table. >> 5. move the mailrelated ip addresses from hostA to hostB. > >> Only during steps 4 and 5 will users experience downtime because of >> the tables locks. Also, you will probably want to stop your MTA from >> inserting new messages during this procedure. > > I want to make sure I understand this. During step 3 (dbmail-util -by) > I can still be running 2.0 against the tables? > You say "you will probably want to stop your MTA from inserting new > messages during this procedure." When? Starting at Step 2? 3? 4?
You can avoid stopping your MTA by adding 6. re-run dbmail-util -by to update the caches for messages inserted during the upgrade. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
