Aleksander wrote: > I don't know what impact it has on performace or integrity, but they > sure got to go. Is it safe to DROP dbmail_messages_ibfk_1 and > dbmail_mailboxes_ibfk_1?
Yes. > The only idea how to make sure everything is OK seams to be to dump the > database. sed s/ the dump file to remove the DROP TABLE IF EXISTS and > CREATE TABLE commands. Create the tables using the create_tables.sql > from latest dbmail and then source the edited dump file. > > sed'ing the dump won't be fun though, it's about 14GBytes. Maybe there's > a way to make mysql ignore DROP and CREATE commands while sourcing the > dump? Sed?? Use: mysqldump --single-transaction --disable-keys --quick dbmail. But actually, drop/reload isn't required. Just make sure the schema are up-to-date: mysqladmin create dbmail2 mysqladmin create dbmail3 mysql dbmail2 < create_tables.mysql mysqldump -d dbmail2 > /tmp/dbmail2.sql mysqldump -d dbmail > /tmp/dbmail3.sql mysql dbmail3 < /tmp/dbmail3.sql diff /tmp/dbmail2.sql /tmp/dbmail3.sql vi alter.sql mysql dbmail3 < alter.sql mysqldump dbmail3 > /tmp/dbmail3.sql diff .... etc... until you're satisfied with the alter.sql file. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
