By "source file", do you mean the source command in the commandline tool mysql? If so, you need to kill that client, not the individual commands in PROCESSLIST.
Go to the OS's task manager. (You may need to be root.)
# ps -axl | grep mysql (or other args of your picking)
# kill -9 1234567 (using the PID from the ps)
Tablenames that are added in (future) version of WordPress should not be a problem when you are scripting this solution
If a take a look at my 'test' database:
CASE TABLE_NAME WHEN 'big' THEN "i<10" ELSE "1" END AS filter
I do see something like this:
You may try to edit your mysqldump file to remove indexes. It's just a text file with SQL statements, so you need to somehow find CREATE TABLE statements in it and remove KEY lines from them (except from PRIMARY KEY). But that can hardly help with the speed because InnoDB index creation is quite efficient and doesn't take overhead time compared to separate ...
The reason is that your mysqldump command is missing some parameters.
There's nothing related about turning Encryption on your RDS instance.
Please add --set-gtid-purged=OFF, --quick and --compress on command parameters that will boost your dump speed:
mysqldump -u test -p -h xxx.aws.com --set-gtid-purged=OFF --quick --compress > dump....
Answer is very simple. -d stands for NO DATA !!!
Here is the MariaDB Documentation:
Do not write any table row information (that is, do not dump table contents). This is useful if you want to dump only the CREATE TABLE statement for the table (for example, to create an empty copy of the table by loading the dump file).
Just get rid of the -d and you are ...
Before posting my question I did just a few more tweaks to see what might be going wrong. I may have stumbled into an answer. So I posted the question anyway and I'm going to post a potential answer here in hopes that it helps the next person.
The -d option in the second row I thought was short for --databases, but it appears to do something else. I don'...