MYLOADER(1)

πŸ’– MYLOADER(1) β€” the mydumper girlies' fave little loader πŸ’–

okay bestie, welcome to myloader, lived in the mydumper manual, and I'm about to make you obsessed with restoring backups. πŸ¦‹


✨ NAME ✨

myloader β€” a multi-threaded MySQL loader 🌈 (yes she multitasks, she's that girl)


✨ SYNOPSIS ✨

myloader --directory = /path/to/mydumper/backup [OPTIONS]

✨ DESCRIPTION ✨

So like, myloader is the tool you use for multi-threaded restoration of mydumper backups. That's it, that's the whole vibe. Dump it with mydumper, load it back with myloader, eat πŸ’…


✨ OPTIONS ✨

The myloader tool has several available options, and we're going through ALL of them because I do not skip. periodt πŸ’–

  • --help, -? β€” shows you the help text. your little cheat sheet, no shame in it πŸŽ€
  • --defaults-file β€” use the option file you point at. and here's the chill part: if the file doesn't exist or is otherwise inaccessible, no failure occurs. she simply moves on 😌
  • --host, -h β€” hostname of the MySQL server to connect to (default is localhost)
  • --user, -u β€” the MySQL username, and she needs the correct privileges to execute the restoration. don't come at her underprivileged, bestie πŸ‘‘
  • --password, -p β€” the corresponding password for that MySQL user πŸ”
  • --port, -P β€” the port for the MySQL connection.
NOTE: for localhost TCP connections use 127.0.0.1 for --host. literally not localhost, use 127.0.0.1. iykyk 😭
  • --socket, -S β€” the UNIX domain socket file to use for the connection
  • --threads, -t β€” the number of threads to use for restoring data, default is 4. four girlies working in parallel, iconic 🧚
  • --version, -V β€” show the program version and exit
  • --compress-protocol, -C β€” use client protocol compression for connections to the MySQL server. squeeze it, slay 🌸
  • --directory, -d β€” the directory of the mydumper backup to restore
  • --database, -B β€” an alternative database to load the dump into
NOTE: this is for use with single database dumps. when using with multi-database dumps that have duplicate table names in more than one database it may cause errors. alternatively this scenario may give unpredictable results with --overwrite-tables. so like, be careful, bestie πŸ’€
  • --source-db, -s β€” database to restore, useful in combination with –database
  • --queries-per-transaction, -q β€” number of INSERT queries to execute per transaction during restore, default is 1000.
  • --overwrite-tables, -o β€” drop any existing tables when restoring schemas. she said out with the old πŸ”₯
  • --enable-binlog, -e β€” log the data loading in the MySQL binary log if enabled (off by default)
  • --verbose, -v β€” the verbosity of messages. 0 = silent, 1 = errors, 2 = warnings, 3 = info. default is 2.

✨ AUTHOR ✨

Andrew Hutchings πŸ’œ


2011, Andrew Hutchings


and that's the whole page, babe 🫢 this was version 0.10.0, dated Sep 22, 2025 β€” go forth and restore, you absolute legend β­πŸŒˆπŸ’–

πŸ“¦ where this page comes from