| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Michael Widenius | Date: | November 13 1999 10:16pm |
| Subject: | Re: mysql is a pain in the ass | ||
| View as plain text | |||
>>>>> "Raul" == Raul Miller <raul@stripped> writes: Raul> On Wed, Nov 03, 1999 at 04:11:55PM +0200, sinisa@stripped wrote: >> Copying a table should not slow down anything, unless you issue LOCKs. Raul> Consider this statement: Raul> insert into users_tmp select * from users; Raul> This must put a reader lock on the users table. This means that no Raul> inserts can proceed against the users table till the statement has Raul> completed. Furthermore, any further selects won't complete till Raul> those inserts have completed. Hi! The above is not true if you prioritize your queries properly. You can always have multiple SELECT running at the same time if you use INSERT DELAYED or start mysqld with --low-priority-updates. Regards, Monty
