Bug #12834 mysqlbinlog does not have tmpdir option.
Submitted: 26 Aug 2005 14:32 Modified: 3 Sep 2010 12:30
Reporter: Tom Krouper Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:4.1.11 OS:FreeBSD (FreeBSD)
Assigned to: Assigned Account CPU Architecture:Any

[26 Aug 2005 14:32] Tom Krouper 
Description:
While using mysqlbinlog I ran into a problem where my /var/tmp directory would fill up. For mysqld I have defined tmpdir. We have several LOAD DATA INFILE commands, and when mysqlbinlog comes across those, it puts a file in /var/tmp. I'd like to be able to define what directory to put these files.

How to repeat:
Load a text file into mysql using mysqlimport or load data infile that is larger than /var/tmp. (log-bin must be on.) Then run mysqlbinlog on the binlog where the text file was imported.

Suggested fix:
Add tmpdir option to mysqlbinlog.
[4 Feb 2008 22:38] Sveta Smirnova 
Thank you for the reasonable feature request.

Can be duplicate of bug #34283 as suggested fix for latter contains more complicated design.
[2 Mar 2009 7:38] Andrew Hutchings 
I believe the -l (--local-load) option provides this with mysqlbinlog in 5.1
[3 Sep 2010 12:30] Sven Sandberg 
This has been fixed in BUG#35546. Use mysqlbinlog --local-load=/path/to/tmp/dir