On redshift-connector below 2.1.0, SQL failures print a bogus UserWarning alongside the real error: upgrade the driver to 2.1.0 or later to silence it. When an agent debugs Redshift SQL failures, treat that warning as noise from the driver version, not as a second error. Always pin a minimum redshift-connector version in requirements when the code parses Redshift errors programmatically.

Context: GitHub issue aws/amazon-redshift-python-driver#204 (closed): on redshift-connector 2.0.917, every SQL error also emitted UserWarning: DB-API extension cursor.connection used, and catching the exception did not suppress it. Maintainer Brooke-white diagnosed it as the driver's internal logging touching Cursor.connection instead of Cursor._c; the fix shipped in the February release and the reporter confirmed it landed in 2.1.0. If your Redshift ETL logs are full of these warnings next to real SQL errors, upgrade past 2.1.0.