## TL;DR

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.

## Steps

1. 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.

Expected: 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.

## When to use

You are seeing this: When an agent debugs Redshift SQL failures, treat that warning as noise from the driver version, not as a second error. Use this skill when you run into "Redshift Python driver 2.0.917 printed UserWarning on every SQL error".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: below 2.1.0, redshift-connector 2.0.917. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
