diff --git a/apps/docs/content/troubleshooting/disabling-prepared-statements-qL8lEL.mdx b/apps/docs/content/troubleshooting/disabling-prepared-statements-qL8lEL.mdx index a96a8db18f3..960f37368f1 100644 --- a/apps/docs/content/troubleshooting/disabling-prepared-statements-qL8lEL.mdx +++ b/apps/docs/content/troubleshooting/disabling-prepared-statements-qL8lEL.mdx @@ -2,8 +2,9 @@ title = "Disabling Prepared statements" github_url = "https://github.com/orgs/supabase/discussions/28239" date_created = "2024-07-28T15:32:23+00:00" -topics = ["database", "supavisor"] -keywords = ["prepared", "statements", "transaction", "mode", "disable"] +topics = [ "database", "supavisor" ] +keywords = [ "prepared", "statements", "transaction", "mode", "disable" ] +database_id = "04801b69-e7eb-4f40-8d41-81110397bbc2" --- ### It is important to note that although the direct connections and Supavisor in Session mode support prepared statements, Supavisor in transaction mode does not. diff --git a/apps/docs/content/troubleshooting/error-prepared-statement-xxx-already-exists-3laqeM.mdx b/apps/docs/content/troubleshooting/error-prepared-statement-xxx-already-exists-3laqeM.mdx index 027743ebfb9..2b5a114f58a 100644 --- a/apps/docs/content/troubleshooting/error-prepared-statement-xxx-already-exists-3laqeM.mdx +++ b/apps/docs/content/troubleshooting/error-prepared-statement-xxx-already-exists-3laqeM.mdx @@ -1,12 +1,13 @@ --- -title = 'Error: prepared statement "XXX" already exists' +title = "Error: prepared statement \"XXX\" already exists" github_url = "https://github.com/orgs/supabase/discussions/17751" date_created = "2023-09-27T09:53:08+00:00" -topics = ["database"] -keywords = ["pgbouncer", "prepared", "connection"] +topics = [ "database" ] +keywords = [ "pgbouncer", "prepared", "connection" ] +database_id = "8688dad6-3dce-4912-9b90-4f128daf79d7" [[errors]] -message = 'prepared statement "XXX" already exists' +message = "prepared statement \"XXX\" already exists" --- This error occurs when you are trying to connect to the database using PgBouncer. PgBouncer does not support prepared statements. If you have prepared statements in use, you will need to use direct connections - port 5432. diff --git a/apps/docs/content/troubleshooting/prisma-error-management-Cm5P_o.mdx b/apps/docs/content/troubleshooting/prisma-error-management-Cm5P_o.mdx index ed1a28fe819..951a09fe7b4 100644 --- a/apps/docs/content/troubleshooting/prisma-error-management-Cm5P_o.mdx +++ b/apps/docs/content/troubleshooting/prisma-error-management-Cm5P_o.mdx @@ -2,8 +2,9 @@ title = "Prisma Error Management" github_url = "https://github.com/orgs/supabase/discussions/27395" date_created = "2024-06-19T19:51:23+00:00" -topics = ["database"] -keywords = ["prisma", "timeout", "connection", "pgbouncer", "schema", "migration"] +topics = [ "database" ] +keywords = [ "prisma", "timeout", "connection", "pgbouncer", "schema", "migration" ] +database_id = "28d842fd-8ba3-46f0-a307-082d946e0d94" [[errors]] message = "Can't reach database server at" @@ -12,7 +13,7 @@ message = "Can't reach database server at" message = "Timed out fetching a new connection from the connection pool" [[errors]] -message = 'prepared statement "" already exists' +message = "prepared statement \"\" already exists" [[errors]] message = "Max client connections reached" diff --git a/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx b/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx index 789cd444bc1..646c14603a7 100644 --- a/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx +++ b/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx @@ -2,8 +2,9 @@ title = "Supavisor and Connection Terminology Explained" github_url = "https://github.com/orgs/supabase/discussions/27388" date_created = "2024-06-19T15:56:26+00:00" -topics = ["supavisor", "database"] -keywords = ["connections", "pooler", "transaction", "session", "pgbouncer"] +topics = [ "supavisor", "database" ] +keywords = [ "connections", "pooler", "transaction", "session", "pgbouncer" ] +database_id = "e008e056-453d-44b5-8a8a-27c2d70681fe" --- I'll be the first to admit that the official naming conventions in the Postgres community can be a bit confusing, so here's a basic rundown. It's a bit long, so feel free to just jump to the portion relevant to you: diff --git a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx index a4a4be7e96e..b0f4b500b27 100644 --- a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx +++ b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx @@ -2,8 +2,9 @@ title = "Supavisor FAQ" github_url = "https://github.com/orgs/supabase/discussions/21566" date_created = "2024-02-26T16:23:40+00:00" -topics = ["supavisor", "database"] -keywords = ["pooler", "connections", "supavisor", "database"] +topics = [ "supavisor", "database" ] +keywords = [ "pooler", "connections", "supavisor", "database" ] +database_id = "f252ba39-e540-462b-868f-42eb31a5d40c" --- ### What Problems Do Poolers Solve? diff --git a/apps/docs/content/troubleshooting/using-sqlalchemy-with-supabase-FUqebT.mdx b/apps/docs/content/troubleshooting/using-sqlalchemy-with-supabase-FUqebT.mdx index 8dadd315924..c32443e9ecb 100644 --- a/apps/docs/content/troubleshooting/using-sqlalchemy-with-supabase-FUqebT.mdx +++ b/apps/docs/content/troubleshooting/using-sqlalchemy-with-supabase-FUqebT.mdx @@ -2,8 +2,9 @@ title = "Using SQLAlchemy with Supabase" github_url = "https://github.com/orgs/supabase/discussions/27071" date_created = "2024-06-06T16:27:43+00:00" -topics = ["database", "supavisor", "self-hosting", "functions"] -keywords = ["sqlalchemy", "ipv6", "pool", "database", "connection"] +topics = [ "database", "supavisor", "self-hosting", "functions" ] +keywords = [ "sqlalchemy", "ipv6", "pool", "database", "connection" ] +database_id = "da4efcda-cd02-4001-965b-f0294300152f" --- ## Deploying to auto-scaling servers: