From a08941c5dc1df0791414732894046d4a4dfc3d7e Mon Sep 17 00:00:00 2001
From: Pablo Martin <pablo.martin@superhog.com>
Date: Fri, 27 Sep 2024 16:29:29 +0200
Subject: [PATCH] comment vacuum analyze to run weekend test

---
 dbt_project.yml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/dbt_project.yml b/dbt_project.yml
index 1f1b5f1..0ad1163 100644
--- a/dbt_project.yml
+++ b/dbt_project.yml
@@ -36,12 +36,13 @@ models:
   # it's very fitting for our needs. You can read more here:
   # https://www.crunchydata.com/blog/postgresl-unlogged-tables
   dwh_dbt:
-    +post-hook:
-      sql: "VACUUM ANALYZE {{ this }}"
-      transaction: false
-      # ^ This makes dbt run a VACUUM ANALYZE on the models after building each.
-      # It's pointless for views, but it doesn't matter because Postgres fails
-      # silently withour raising an unhandled exception.
+    # VVVVVVVVVVV Commented for testing purposes. We probably wanna uncomment eventually!!!
+    #  +post-hook:
+    #    sql: "VACUUM ANALYZE {{ this }}"
+    #    transaction: false
+    # ^ This makes dbt run a VACUUM ANALYZE on the models after building each.
+    # It's pointless for views, but it doesn't matter because Postgres fails
+    # silently withour raising an unhandled exception.
     staging:
       +materialized: table
       +schema: staging