Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nw5Q2-00014m-4X for pgsql-docs@arkaria.postgresql.org; Tue, 31 May 2022 17:12:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nw5Q0-0000sH-7s for pgsql-docs@arkaria.postgresql.org; Tue, 31 May 2022 17:12:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nw5Cb-0005X7-AS for pgsql-docs@lists.postgresql.org; Tue, 31 May 2022 16:58:41 +0000 Received: from mail-vs1-xe30.google.com ([2607:f8b0:4864:20::e30]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nw5CW-0000u3-Dw for pgsql-docs@lists.postgresql.org; Tue, 31 May 2022 16:58:40 +0000 Received: by mail-vs1-xe30.google.com with SMTP id i186so14172293vsc.9 for ; Tue, 31 May 2022 09:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rvD/eMSwj9BOmENPMyQQ+TdVICKaGBX6mR+osYInH0k=; b=aJW6mFX2EZO+HU1QczNpUGUAXVFuJMWZBTJcbR+DRPHkjk6C/xN+yMGTL8CMZYb7cD yTlIIL2oWFdfVowHNh4Xe1XtwWuhX8TpAzTv2CQmwf4PFUKMG0jSd00pNvFjbbgbiLHO oGXcmB/UaQT9YA2xwA7uAie7rKEJuYvO5bEzlkW3SFwpLdO/iltHLWW/WV5QghHa6kFe PRdmv68KWHG17Bch/gsbX0oJoiV+R70dpL/EWVRgHe1lxUIHvDicceOxkFkn2OGo/zjz qSCffn0GZVq8sMcgOz8F01kln49RAVcTHWQ2u72jSuk1hoYNHlvVRNuWCZldh4qbe1tw PqcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rvD/eMSwj9BOmENPMyQQ+TdVICKaGBX6mR+osYInH0k=; b=beZbh+5mrLalM7A9fZvbU1U0nK0bVMBLQv0TsSZqSqw3TQsdxv0rUDVZYBK3CI0U17 EjHb3tbbFZ5XhX7fZ6+FShxGRr3TqK33uxQ26ivANxTSpMgDKRDwLiGNNKs8ghSQ5doT HavZBHjhJg4OspPctEXa3NyRJrBWYbTSvNbZzQ36H+Vt0vScw2cT9Vb9fPUti+v4RSwu hTCAORUdxMXJ6yZqhWOn2bUPcYN3c4rjFHSD4grqCbWNWwe0tfkw0kwM+7e6rL3Y9N9L kEyf1+O9RIL2es5pWpVcDQSBuf/iBNCE7V/R/6BLZ50Y9wOh8YJ8D0yJ8QR/2thmitnp 6uWw== X-Gm-Message-State: AOAM532R72hXDE1DmCpqbnPrfzGywF6yYoa9mqs93i4nT/T5Uwn/9JiW BNkL4davEnRUoWFSjNATNXa4Ez7dulSuBs9xEdA= X-Google-Smtp-Source: ABdhPJw5cxABU6LB6okSxQccjAwjTawzwtxXoW0PdUHWWiHjImnjKGKFdaXwqatplEi/bPTJnFG9qZrkoYNP1+zdHJg= X-Received: by 2002:a67:2283:0:b0:339:8b9e:433b with SMTP id i125-20020a672283000000b003398b9e433bmr9847273vsi.7.1654016315055; Tue, 31 May 2022 09:58:35 -0700 (PDT) MIME-Version: 1.0 References: <165400680669.573549.5553646427767597793@wrigleys.postgresql.org> <184838.1654011177@sss.pgh.pa.us> In-Reply-To: <184838.1654011177@sss.pgh.pa.us> From: Gustavo Date: Tue, 31 May 2022 13:58:24 -0300 Message-ID: Subject: Re: CREATE EXTENSION not adding extension on second SCHEMA To: Tom Lane Cc: "David G. Johnston" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000e965ba05e051ae76" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e965ba05e051ae76 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you so much guys, my mistake I didn't pay attention. I'm new to PostgreSQL and your help is much appreciated! Em ter., 31 de mai. de 2022 =C3=A0s 12:32, Tom Lane esc= reveu: > "David G. Johnston" writes: > > On Tuesday, May 31, 2022, PG Doc comments form > > wrote: > >> I'm trying to add an extension to two schemas that I have in my DB. > > > It doesn=E2=80=99t work and isn=E2=80=99t documented as something that = does work. I > really > > don=E2=80=99t see a need to say you cannot install the same extension m= ultiple > > 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 > --000000000000e965ba05e051ae76 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you so much guys, my mistake I didn= 't pay attention. I'm new to=C2=A0PostgreSQL and your help is much = appreciated!



Em ter., 31 de mai. de 2022 =C3=A0s 12:32, Tom Lane= <tgl@sss.pgh.pa.us> escreve= u:
"David G= . Johnston" <david.g.johnston@gmail.com> writes:
> On Tuesday, May 31, 2022, PG Doc comments form <noreply@postgresql.org>
> wrote:
>> I'm trying to add an extension to two schemas that I have in m= y DB.

> It doesn=E2=80=99t work and isn=E2=80=99t documented as something that= does work.=C2=A0 I really
> don=E2=80=99t 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.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane
--000000000000e965ba05e051ae76--