From dcd4bf6fae3c89d7bf06bc2e784b51616e378d3d Mon Sep 17 00:00:00 2001 From: Yeganathan S Date: Mon, 7 Feb 2022 23:09:50 +0530 Subject: [PATCH] docs: improve docs for enabling extensions(#4968) --- web/docs/guides/database/extensions.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/web/docs/guides/database/extensions.mdx b/web/docs/guides/database/extensions.mdx index bfdbd035827..3c58d9cde8b 100644 --- a/web/docs/guides/database/extensions.mdx +++ b/web/docs/guides/database/extensions.mdx @@ -43,8 +43,8 @@ values={[ ```sql --- Example: enable the "pgtap" extension -create extension pgtap; +-- Example: enable the "pgtap" extension and ensure it is installed +create extension pgtap with schema extensions; -- Example: disable the "pgtap" extension drop extension pgtap; @@ -54,6 +54,8 @@ drop extension pgtap; Even though the SQL code is `create extension`, this is the equivalent of "enabling the extension". To disable an extension you can call `drop extension`. +Enabling few extensions by the SQL code `create extension with schema extensions` may lead to permission issues (e.g. `dblink`, `http`, `pg_cron`). +