[SPIKE] Investigate state of transactions

[dataders]

Is this your first time submitting a feature request?

• [X] I have read the expectations for open source contributors
• [X] I have searched the existing issues, and I could not find an existing issue for this feature
• [X] I am requesting a straightforward extension of existing dbt-redshift functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Several issues already exist that even today, transactions are not working in dbt-redshift as they should

Similar to https://github.com/dbt-labs/dbt-adapters/issues/347 but only for dbt-redshift. Less future looking, but rather backward looking. How can we get back to a previous state?

questions

• Will https://github.com/aws/amazon-redshift-python-driver/issues/162 solve our problems, or is there more to do?
• how does the autocommit parameter introduced in dbt-labs/dbt-core#475 affect transaction behavior?
• is there a way to expose redshift_connector's .commit() method to users in jinja land instaed?

### Transaction-related open issues
- [ ] dbt-labs/dbt-core#521 
- [ ] dbt-labs/dbt-core#663
- [ ] dbt-labs/dbt-core#693
- [ ] dbt-labs/dbt-core#741
- [ ] dbt-labs/dbt-core#766

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

[victor-frank-signet]

I want to add that is this a problem with redshift_connector AND the redshift version? Some people say it started in 1.5+. But once the bug was reported others have said if they downgraded from 1.5+ to 1.4 and 1.4 the error persists.

https://github.com/dbt-labs/dbt-redshift/issues/766#issuecomment-2078339621 https://github.com/dbt-labs/dbt-redshift/issues/501#issuecomment-1604466970