On Thu, Jul 31, 2008 at 1:28 PM, Roger Searle <[EMAIL PROTECTED]> wrote: > Hi, I have a mediawiki installation working well, and can back up using > phpMyAdmin or via "mysqldump -u root -p dbname > "backup.sql" to create .sql > files. On testing my restore method I noted that phpMyAdmin was limited by > default to a 2MB text file for importing, and my backup file exceeds this, > giving the error "the file size exceeded the maximum size permitted by your > PHP configuration". (I have no doubt this could be changed somewhere if I > were to investigate how/where. Should anyone like to answer that point, > great, but primarily I'm interested in a different matter.)
look at your php configuration, I am sure there is a quite simple setting in there. > > So I explored importing the .sql dumps (created by both above methods) via > command line and can happily ssh to the server, log in to mysql and execute > a "drop database dbname" and "create database dbname" commands, quit mysql > and do "mysql -u root -p dbname < backup.sql". With both backup methods, the > restores seem to be successful in that the restored wiki becomes available > for viewing, recent changes can be viewed etc, all appears to be fine. > The reason for this post is to seek feedback about why the 2 backup methods > produce quite different file sizes: via phpMyAdmin I get a 2.8 MB file, via > mysqldump it is only 1.5 MB. Is something being omitted by the mysqldump > method? Or is the phpMyAdmin method bloated in some (deliberate?) way or > less efficient in it's file creation? Or backs up additional folders? > Something else? > > Any pointers as to what might explain this, or other gotchas to look out > for, would be appreciated. The backup files should be plain text, try taking a look at them. It could be extra whitespace, depending on how the backup program formats it's output.
