Hello. Usually clients are blocked with insert or update statements until table became unlocked. Their threads just sleep and then continue execution (but they can got an error if query doesn't return for a long time). INSERT queries are not buffered in that sense you've ment, unlike they are INSERT DELAYED. May be you should think about incremental backup. See: http://dev.mysql.com/doc/mysql/en/Backup.html
[EMAIL PROTECTED] wrote: > [-- text/plain, encoding 8bit, charset: US-ASCII, 14 lines --] > > Hi all, > > > Looking for a way to automate backup I was thinking of scheduling mysqldump > on a daily base. It want to use the read lock, but I am not really sure about > the consequences of this. > Does putting a read lock on the files can cause loss of data? > It is no problem pausing the flow of incoming data (invoices and other > documents that are put in a monitored directory). > But what about the data coming from the application that accesses the > database? Say a user changes preferences or creates a new query, which are > saved in the database. Is that data lost or buffered by MySql? Or does the > application have to provide functionality to anticipate his situation? > I know, I could bring down the whole system (webserver, application services > and MySql), but with the read lock, the system would be 'down' (querying > still possible) for only half an hour and it keeps running. > The platform is Win2K. > > > Regards, > > Olivier -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
