On Thu, Sep 7, 2017, at 02:04 PM, shawn l.green wrote: > Hello Josh, > > > What appears to be missing on that page is a discussion what to do with > the "temporary tablespace" used to hold intrinsic (internal) temporary > tables created by different types of queries you could execute. > > https://dev.mysql.com/doc/refman/5.7/en/innodb-temporary-tablespace.html > > https://dev.mysql.com/doc/refman/5.7/en/internal-temporary-tables.html > > If you point the setting --innodb-temp-data-file-path to a location that > is writeable (and accessible to the user that your mysqld is running > as), does that get you past this problem? > > https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_temp_data_file_path > > Think of it as allocating "scratch space" for this mysqld to "think" > while it processes your queries against the data. > > Yours, > -- > Shawn Green > MySQL Senior Principal Technical Support Engineer > Oracle USA, Inc. - Integrated Cloud Applications & Platform Services > Office: Blountville, TN > > Become certified in MySQL! Visit https://www.mysql.com/certification/ > for details. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql >
Shawn, That was exactly the problem. Thanks for the reply. https://bugs.mysql.com/?id=87697 -- Thanks, Josh Paetzel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
