I've tested this behavior with Redshift ODBC 2.0.0.8 & 2.0.0.9 The Problem occurs when attempting to load lots of data through ODBC when Redshift has a too small max_query_execution_time. After the ...