Actually, analyze also locks the table, albeit a read-lock only. Other than that, sounds valid enough to me.
Lars Kneschke wrote: > Hello! > > When we call dbmail-util with the option -c or -a, all dbmail tables get > optimized. Which means copying the tables physicaly from one location to > another and updating the statistics. While copying the tables, they are > locked for inserts. On a big database this can take some time. > > I'm not sure if we really need to optimize the tables. I think it is > enough to analyze the tables only. When you analyze the tables, the > counters(needed by the query analyzer/optimizer) get updated. While > analyzing the tables, they don't get locked. > > I propose switching to analyze tables instead of optimize tables. Maybe > we can also execute analyze tables with another option. > > But executing optimize tables every day to expensive. Calling analyze > tables every day is cheap. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
