From c7ae3ec61f9192a55b0d1513ef1e464f15afbadd Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Wed, 6 Nov 2024 19:53:16 -0700
Subject: [PATCH] Logging relational cache events

---
 website/docs/reference/global-configs/cache.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/website/docs/reference/global-configs/cache.md b/website/docs/reference/global-configs/cache.md
index 1a74fef8d30..52d1f8d4e76 100644
--- a/website/docs/reference/global-configs/cache.md
+++ b/website/docs/reference/global-configs/cache.md
@@ -6,7 +6,7 @@ sidebar: "Cache"
 
 ### Cache population
 
-At the start of runs, dbt caches metadata about all the objects in all the schemas where it might materialize resources (such as models). By default, dbt populates the cache with information on all schemas related to the project.
+At the start of runs, dbt caches metadata about all the objects in all the schemas where it might materialize resources (such as models). By default, dbt populates the relational cache with information on all schemas related to the project.
 
 There are two ways to optionally modify this behavior:
 - `POPULATE_CACHE` (default: `True`): Whether to populate the cache at all. To skip cache population entirely, use the `--no-populate-cache` flag or `DBT_POPULATE_CACHE: False`. Note that this does not _disable_ the cache; missed cache lookups will run queries, and update the cache afterward.
@@ -26,3 +26,11 @@ Or, to improve speed and performance while focused on developing Salesforce mode
 dbt --cache-selected-only run --select salesforce
 
 ```
+
+### Logging relational cache events
+
+The `LOG_CACHE_EVENTS` config allows detailed logging for relational cache events, which are disabled by default.
+
+```text
+dbt --log-cache-events compile
+```