From b4bada070b7e2ebb94bf64cfadc33526ccb62147 Mon Sep 17 00:00:00 2001 From: Arjun Kohli <74593435+Arjun3492@users.noreply.github.com> Date: Mon, 15 Jan 2024 20:18:00 +0530 Subject: [PATCH] updated doc for specifying installation of custom SQL extensions (#14600) updated doc for specifying installation of custom SQL extemsions Co-authored-by: Terry Sutton --- apps/docs/pages/guides/database/extensions.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/apps/docs/pages/guides/database/extensions.mdx b/apps/docs/pages/guides/database/extensions.mdx index d89058b02db..daaf0921efb 100644 --- a/apps/docs/pages/guides/database/extensions.mdx +++ b/apps/docs/pages/guides/database/extensions.mdx @@ -53,6 +53,8 @@ If you need to restrict user access to tables managed by extensions, we recommen Some extensions can only be created under a specific schema, for eg. `postgis_tiger_geocoder` extension creates a schema named `tiger`. Before enabling such extensions, make sure you have not created a conflicting schema with the same name. +In addition to the pre-configured extensions, you can also install your own SQL extensions directly in the database using Supabase's SQL editor. The SQL code for the extensions, including plpgsql extensions, can be added through the SQL editor. + ### Full list of extensions