| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Michael Widenius | Date: | January 5 2000 2:33am |
| Subject: | Re: CONCURRENT_INSERT? | ||
| View as plain text | |||
>>>>> "Tim" == Tim Bunce <Tim.Bunce@stripped> writes: Tim> On Wed, Jan 05, 2000 at 01:35:19AM +0200, Michael Widenius wrote: >> >> It works instead as follows (this is done in an atomic context without >> giving any other threads any possibility to interfere) >> >> - Get a write-insert-lock >> - Check if the table has any deleted blocks; If this is true, >> upgrade the lock to a write_lock and continue without concurrent inserts. Tim> What's the fastest/cheapest way to remove deleted blocks? "Optimize"? isamchk -r -O sort_buffer=128M */*.MYI is faster (if you have > 128M memory), but optimize is the fastest way from withing MySQL. Regards, Monty
| Thread | ||
|---|---|---|
| • CONCURRENT_INSERT? | Dylan Neild | 13 Dec |
| • Re: CONCURRENT_INSERT? | sinisa | 13 Dec |
| • Re: CONCURRENT_INSERT? | Tonu Samuel | 14 Dec |
| • CONCURRENT_INSERT? | Michael Widenius | 5 Jan |
| • Re: CONCURRENT_INSERT? | Tim Bunce | 5 Jan |
| • Re: CONCURRENT_INSERT? | Michael Widenius | 5 Jan |
| • Re: CONCURRENT_INSERT? | Tim Bunce | 5 Jan |
| • RE: CONCURRENT_INSERT? | Steven Roussey | 6 Jan |
| • RE: CONCURRENT_INSERT? | sinisa | 6 Jan |
| • RE: CONCURRENT_INSERT? | Michael Widenius | 6 Jan |
| • Re: CONCURRENT_INSERT? | elble | 6 Jan |
| • Re: CONCURRENT_INSERT? | Michael Widenius | 7 Jan |
| • RE: CONCURRENT_INSERT? | Andy | 6 Jan |
