[bot] sync troubleshooting guides to db (#32889)

Co-authored-by: github-docs-sync-bot <github-docs-sync-bot@supabase.com>

apps/docs/content/troubleshooting/discovering-and-interpreting-api-errors-in-the-logs-7xREI9.mdx

@@ -2,8 +2,9 @@
 title = "Discovering and Interpreting API Errors in the Logs"
 github_url = "https://github.com/orgs/supabase/discussions/22849"
 date_created = "2024-04-18T02:38:44+00:00"
-topics = ["database", "platform"]
-keywords = ["logs", "api", "errors", "postgrest", "cloudflare"]
+topics = [ "database", "platform" ]
+keywords = [ "logs", "api", "errors", "postgrest", "cloudflare" ]
+database_id = "188986c9-019d-4f26-baaf-6f58cec8fa7a"
 ---
 
 > A complimentary [guide](https://github.com/orgs/supabase/discussions/26224) was made for the Postgres logs

apps/docs/content/troubleshooting/fetch-requests-to-api-endpoints-arent-showing-the-session-UbUwRs.mdx

@@ -2,8 +2,9 @@
 title = "Fetch requests to API endpoints aren't showing the session"
 github_url = "https://github.com/orgs/supabase/discussions/15859"
 date_created = "2023-07-18T12:22:14+00:00"
-topics = ["auth"]
-keywords = ["session", "cookie"]
+topics = [ "auth" ]
+keywords = [ "session", "cookie" ]
+database_id = "6f19b113-09cb-45ce-8141-0d6dc10ea464"
 ---
 
 You must pass along the cookie header with the fetch request in order for your API endpoint to get access to the cookie from this request.

apps/docs/content/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx

@@ -2,7 +2,8 @@
 title = "How to Interpret and Explore the Postgres Logs"
 github_url = "https://github.com/orgs/supabase/discussions/26224"
 date_created = "2024-05-12T21:19:37+00:00"
-topics = ["database", "platform"]
+topics = [ "database", "platform" ]
+database_id = "8b000bb4-180b-4a6c-b280-ba02965060f6"
 ---
 
 > A complimentary guide was made for the [API logs](https://github.com/orgs/supabase/discussions/22849)

apps/docs/content/troubleshooting/understanding-postgresql-explain-output-Un9dqX.mdx

@@ -2,11 +2,12 @@
 title = "Understanding PostgreSQL EXPLAIN Output"
 github_url = "https://github.com/orgs/supabase/discussions/22839"
 date_created = "2024-04-17T16:31:47+00:00"
-topics = ["database"]
-keywords = ["explain", "performance", "query"]
+topics = [ "database" ]
+keywords = [ "explain", "performance", "query" ]
+database_id = "0ce5b1e4-bd0a-439e-9fb1-8e27bad2ef10"
 
 [api]
-sdk = ["explain"]
+sdk = [ "explain" ]
 ---
 
 ### Introduction

apps/docs/content/troubleshooting/understanding-postgresql-logging-levels-and-how-they-impact-your-project-KXiJRm.mdx

@@ -2,8 +2,9 @@
 title = "Understanding PostgreSQL Logging Levels and How They Impact Your Project"
 github_url = "https://github.com/orgs/supabase/discussions/29877"
 date_created = "2024-10-14T09:17:02+00:00"
-topics = ["database"]
-keywords = ["logging", "disk", "i/o", "lockups"]
+topics = [ "database" ]
+keywords = [ "logging", "disk", "i/o", "lockups" ]
+database_id = "10186830-8cce-4f10-8cb9-7cbf39310763"
 ---
 
 Since each Supabase project uses PostgreSQL as its underlying database engine, it’s common to adjust logging settings for various reasons—whether for debugging issues, monitoring database performance, or auditing actions. However, modifying logging levels improperly can lead to an excessive amount of log data being generated, which can quickly fill up your disk space and cause significant performance degradation or even system failure.