Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

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

Chris Chinchillabd72526e04aa
diff --git a/apps/docs/content/troubleshooting/running-explain-analyze-on-functions.mdx b/apps/docs/content/troubleshooting/running-explain-analyze-on-functions.mdx
index 9e7696711e2..301060ffdd0 100644
--- a/apps/docs/content/troubleshooting/running-explain-analyze-on-functions.mdx
+++ b/apps/docs/content/troubleshooting/running-explain-analyze-on-functions.mdx
@@ -1,11 +1,11 @@
---
title = "Running EXPLAIN ANALYZE on functions"
-topics = ["database", "functions"]
-keywords = [] # any strings (topics are automatically added so no need to duplicate)
+topics = [ "database", "functions" ]
+keywords = []
database_id = "1d62cace-c0f6-47a0-8690-002a797da33b"
[api]
-sdk = ["rpc"]
+sdk = [ "rpc" ]
---
Sometimes it can help to look at Postgres query plans inside a function. The problem is that running [`EXPLAIN ANALYZE`](https://www.depesz.com/2013/04/16/explaining-the-unexplainable/) on a function usually just shows a [function scan](https://pganalyze.com/docs/explain/scan-nodes/function-scan) or result node, which gives little insight into how the queries actually perform.