[Bug] Materialized views are executing additional SQL statements during refresh through dbt core

[karthickGK4794]

Is this a new bug in dbt-redshift?

• I believe this is a new bug in dbt-redshift
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

While refreshing the materialized views through dbt core, i see some additional SQL statements are getting executed by dbt such as drop statements of backup and temp tables, view definition and tables svv_table_info, svv_mv_info along with the refresh statement which is taking additional time to refresh the model. Is there a way to avoid running those additional steps to reduce the overall runtime as refresh statement alone is sufficient ?

Expected Behavior

Execution of Refresh materialized view table_name alone

Steps To Reproduce

{{
config({
"materialized":"materialized_view",
"tags": "materialized_Views",
"alias":"table_1"
})
}}

select * from datalake_table

dbt run -s table_1

Relevant log output

select
            tb.database,
            tb.schema,
            tb.table,
            tb.diststyle,
            tb.sortkey1,
            mv.autorefresh
        from svv_table_info tb
        -- svv_mv_info is queryable by Redshift Serverless, but stv_mv_info is not
        left join svv_mv_info mv
            on mv.database_name = tb.database
            and mv.schema_name = tb.schema
            and mv.name = tb.table
        where tb.table ilike 'table_1'
        and tb.schema ilike ''
        and tb.database ilike ''

select
            vw.definition
        from pg_views vw
        where vw.viewname = ''
        and vw.schemaname = ''
        and vw.definition ilike '%create materialized view%'

refresh materialized view table_1

drop materialized view if exists table_1__dbt_backup

drop materialized view if exists table_1__dbt_tmp

Environment

- OS: Windows
- Python:3.9.13
- dbt-core: 1.8.5
- dbt-redshift: 1.8.1

Additional Context

No response