Tables become unavailable during run with Postgres

[chogovadze]

Hello everyone,

I am running DBT through the Cloud service and was wondering if there is anything that is preventing tables to be replaced only after the computation has finished.

Specifically every time the job runs the table becomes unavailable until the job has finished unlike what is described in the documentation:

Nope! The SQL that dbt generates behind the scenes ensures that any relations are replaced atomically (i.e. your business users won't experience any downtime).

The implementation of this varies on each warehouse, check out the logs to see the SQL dbt is executing.

I imagine this is a limitation with Postgres or something that I have misconfigured. In the community forum there was mention of blue/green deployment though this seems to be unnecessarily complicated for the simple use case I have.

Thank you for your time!

The table is defined with the following config:

{{
  config(
    materialized = 'table',
    indexes=[
        {'columns': ['col1'], 'type': 'hash'},
        {'columns': ['col2'], 'type': 'hash'},
        {'columns': ['col3'], 'type': 'hash'},
        {'columns': ['col4'], 'type': 'hash'},
        {'columns': ['col5'], 'type': 'hash'},
        {'columns': ['col6'], 'type': 'btree'},
        {'columns': ['col1', 'col2', 'col3'], 'unique': true}
    ]
    )
}}