[SPIKE] Investigate state of transactions

[dataders]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• 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 dbt-labs/dbt-adapters#347 but only for dbt-redshift. Less future looking, but rather backward looking. How can we get back to a previous state?

questions

• Will support multi-statement .execute() calls aws/amazon-redshift-python-driver#162 solve our problems, or is there more to do?
• how does the autocommit parameter introduced in relocate docs to readme 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

Beta Give feedback

1. materialization config validations dbt-core#521
   enhancement +1
   
2. whitelist loggers instead of blacklisting nonexhaustively dbt-core#663
   bug +1
3. fix statements in on run start hooks dbt-core#693
   +0
4. use a materialization to load csv files dbt-core#741
   +0
5. dbt deps - symlink fails on windows (symbolic link privilege not held) dbt-core#766
   bug +1

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.

#766 (comment)
#501 (comment)