| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Alex Schaft | Date: | October 21 2011 12:02pm |
| Subject: | Re: Maximum line length or statement length for mysqldump | ||
| View as plain text | |||
On 2011/10/21 10:26 AM, Johan De Meersman wrote: > ----- Original Message ----- >> From: "Alex Schaft"<alexs@stripped> >> >> Got my app reading in a dump created with extended-inserts off, and >> lumping all of the insert statements together. Works like a charm > Just for laughs, would you mind posting the on-disk size of your database, and the > restore time with both extended and single inserts? > > ibdata1 currently sitting at 6 gigs. Without ext inserts about a minute and a half and with a couple of seconds. I'm well aware of the speed differences. That's why I'm now reading in the non extended and joining the values together into big sql statements. This now takes about 10 seconds, but I'm still optimizing that.
| Thread | ||
|---|---|---|
| • Maximum line length or statement length for mysqldump | Alex Schaft | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Alex Schaft | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Johan De Meersman | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Alex Schaft | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Johan De Meersman | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Johnny Withers | 20 Oct |
| • Re: Maximum line length or statement length for mysqldump | Alex Schaft | 21 Oct |
| • Re: Maximum line length or statement length for mysqldump | Johan De Meersman | 21 Oct |
| • Re: Maximum line length or statement length for mysqldump | Alex Schaft | 22 Oct |
