diff --git a/website/docs/reference/resource-configs/postgres-configs.md b/website/docs/reference/resource-configs/postgres-configs.md index d5960231c66..c4d60ba905d 100644 --- a/website/docs/reference/resource-configs/postgres-configs.md +++ b/website/docs/reference/resource-configs/postgres-configs.md @@ -116,83 +116,6 @@ with the following configuration parameters: | `on_configuration_change` | | no | `apply` | n/a | | [`indexes`](#indexes) | [{}] | no | `none` | alter | - - - - - - -```yaml -models: - [](/reference/resource-configs/resource-path): - [+](/reference/resource-configs/plus-prefix)[materialized](/reference/resource-configs/materialized): materialized_view - [+](/reference/resource-configs/plus-prefix)on_configuration_change: apply | continue | fail - [+](/reference/resource-configs/plus-prefix)[indexes](#indexes): - - columns: [] - unique: true | false - type: hash | btree -``` - - - - - - - - - - -```yaml -version: 2 - -models: - - name: [] - config: - [materialized](/reference/resource-configs/materialized): materialized_view - on_configuration_change: apply | continue | fail - [indexes](#indexes): - - columns: [] - unique: true | false - type: hash | btree -``` - - - - - - - - - - -```jinja -{{ config( - [materialized](/reference/resource-configs/materialized)="materialized_view", - on_configuration_change="apply" | "continue" | "fail", - [indexes](#indexes)=[ - { - "columns": [""], - "unique": true | false, - "type": "hash" | "btree", - } - ] -) }} -``` - - - - - - - The `indexes` parameter corresponds to that of a table, as linked above. It's worth noting that, unlike with tables, dbt will monitor this parameter for changes and apply the changes without dropping the materialized view. This happens via a `DROP/CREATE` of the indexes, which could be thought of as a `ALTER` of the materialized view.