From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "gustavomilc(at)gmail(dot)com" <gustavomilc(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: CREATE EXTENSION not adding extension on second SCHEMA |
Date: | 2022-05-31 15:24:33 |
Message-ID: | CAKFQuwYyQaDsBRjKGn2ewqLDdMcTJbdLF6-fH2z3zrpRv61t-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tuesday, May 31, 2022, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-createextension.html
> Description:
>
> I'm trying to add an extension to two schemas that I have in my DB.
>
> steps:
>
> 1)
>
> CREATE EXTENSION unaccent with SCHEMA public;
>
> response: OK.
>
> 2)
>
> CREATE EXTENSION unaccent with SCHEMA public_test;
>
> response: SQL Error [42710]: ERROR: extension "unaccent" already exists
>
> I tryed:
>
> SET search_path = public_test;
> CREATE EXTENSION unaccent;
>
> and the response is: response: SQL Error [42710]: ERROR: extension
> "unaccent" already exists
>
It doesn’t work and isn’t documented as something that does work. I really
don’t see a need to say you cannot install the same extension multiple
times explicitly - the self-describing error seems sufficient.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Shetty | 2022-05-31 15:28:43 | Fwd: Adding more detail to pg_upgrade documentation |
Previous Message | jian he | 2022-05-31 15:21:55 | Re: CREATE EXTENSION not adding extension on second SCHEMA |