As the question states, what (if any) is the effect of max_allowed_packet on LOAD LOCAL INFILE?
Does setting it to a large value load data files of large size such as 700MB into the db quickly?
|
As the question states, what (if any) is the effect of Does setting it to a large value load data files of large size such as 700MB into the db quickly? |
||||
|
|
There is no constraint like You can load a GBs file. Depending on the size of the rows, you'll probably exceed this.One way would be to split it up into several chunks. This is probably a good idea anyway. LOAD DATA isn't subject to the If you are adjusting your Set it as
otherwise you may face the issue like
If you face the above error set Otherwise in my opinion increasing it to some higher value will not allow you to quickly load a 700MB file. |
||||
|
|
|
LOAD DATA INFILE can be thrown off if read_buffer_size is larger than max_allowed_packet. This is the case when it comes to replication. See the following bug reports
Outside of MySQL Replication, I can't really tell. One thing is for sure: Whatever mysql had as the setting for max_allowed_packet on a server that performed The max value for max_allowed_packet is 1G. It couldn't hurt to just set that in my.cnf.
You do not have to restart mysql. Just run this:
then you can perform the LOAD DATA INFILE. |
||||
|
|