public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: David G. Johnston <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: CREATE EXTENSION not adding extension on second SCHEMA
Date: Tue, 31 May 2022 11:32:57 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwYyQaDsBRjKGn2ewqLDdMcTJbdLF6-fH2z3zrpRv61t-g@mail.gmail.com>
References: <[email protected]>
	<CAKFQuwYyQaDsBRjKGn2ewqLDdMcTJbdLF6-fH2z3zrpRv61t-g@mail.gmail.com>

"David G. Johnston" <[email protected]> writes:
> On Tuesday, May 31, 2022, PG Doc comments form <[email protected]>
> wrote:
>> I'm trying to add an extension to two schemas that I have in my DB.

> 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.

The CREATE EXTENSION reference page says

"There must not be an extension of the same name already loaded."

and later

"Remember that the extension itself is not considered to be within any
schema: extensions have unqualified names that must be unique
database-wide. But objects belonging to the extension can be within
schemas."

I hardly see how we could make this any plainer.

			regards, tom lane

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: CREATE EXTENSION not adding extension on second SCHEMA
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox