Workaround dbt-fusion 2.0.0-preview.104 Redshift temp table bug

Disable temporary tables for Redshift when using dbt-fusion to work around
a panic in preview.104's ADBC 0.22 driver.

Bug: get_columns_in_relation() on temp tables causes intermittent panics with:
"Either resolved_catalog or resolved_schema must be present"
at fs/sa/crates/dbt-adapter/src/metadata/mod.rs:91:9

The panic occurs during INSERT operations when the ADBC driver returns empty
catalog/schema metadata for temporary tables.

Workaround: Disable temp tables for Redshift+fusion, using regular tables
instead. This is slightly less efficient but avoids the panic.

This bug was introduced in preview.104 and was not present in preview.102.
Will re-enable temp tables once dbt-fusion fixes this issue.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: haritamar

macros/utils/table_operations/has_temp_table_support.sql

@@ -26,3 +26,22 @@
     {% do return(false) %}
 {% endmacro %}
 
+{% macro redshift__has_temp_table_support() %}
+    {# Workaround for dbt-fusion 2.0.0-preview.104 ADBC 0.22 bug
+       where get_columns_in_relation returns empty catalog/schema for temp tables
+       causing panic: "Either resolved_catalog or resolved_schema must be present"
+       at fs/sa/crates/dbt-adapter/src/metadata/mod.rs:91:9
+
+       This occurs intermittently during INSERT operations on temporary tables.
+       Disabling temp tables for Redshift+fusion uses regular tables instead,
+       which is slightly less efficient but avoids the panic.
+
+       Bug introduced in preview.104, not present in preview.102.
+       TODO: Re-enable once dbt-fusion fixes this in a future release. #}
+    {% if elementary.is_dbt_fusion() %}
+        {% do return(false) %}
+    {% else %}
+        {% do return(true) %}
+    {% endif %}
+{% endmacro %}
+