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 1nw3jb-0005Wk-Dt for pgsql-docs@arkaria.postgresql.org; Tue, 31 May 2022 15:24:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nw3ja-0007wB-8E for pgsql-docs@arkaria.postgresql.org; Tue, 31 May 2022 15:24:38 +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 1nw3ja-0007w2-0l for pgsql-docs@lists.postgresql.org; Tue, 31 May 2022 15:24:38 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nw3jX-0008Vd-Le for pgsql-docs@lists.postgresql.org; Tue, 31 May 2022 15:24:37 +0000 Received: by mail-ej1-x62f.google.com with SMTP id f9so27425528ejc.0 for ; Tue, 31 May 2022 08:24:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=79NR15tyODr/yt0Xeoio1VY2sF+MNbqBVO0EM578iQ8=; b=CdhKxZGCHK1CR09XUhZRW/8L1CQZAqAKhj3unILSIvubsDcAaHd567JURKlRvC8fNw TTjC3chdUYPrO2wNPMi6mTzLmQfXIj4EfJ1GIbRF/fLbrjKiCa3xRr4t0sxfvNkTKZQj CYbzE3A89HIn1nzbqRATCfTKROkMwVFH7nwR3rRYTUMuYkEu7/4ySzEEx/MKkGjUIU1F 3mUzkync3bZ/Xjb3lWypJQm+Z9JM5AYzbsihwlSVSRMLENo3eJXNkDDBHoXbnHbzWdGD Sb2GZw00a7a/XPeGvED7lKS0u1CVO3KSqfo0ZCZoTaKbMo+MnjMIV4Xym39hpzhq8p9O Couw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=79NR15tyODr/yt0Xeoio1VY2sF+MNbqBVO0EM578iQ8=; b=d3XweSL8VJcxHM1A/p/Djt0n3wVkq7Dx084m7gIjN3v3NPLPywAV2DkL61szcjRQ/k TFaBEPd7TP/gnMIObrEjpxfdimtS2ENjH7F3X1OsWH5ecqhuB20RFILgy/kxOjVaehvr nMDov5Wf5IX+Vm9o8BByZDIvJY7YKhZcylCHxiQHC4IjNQZfBRrtA0g+UAl7j3TEAz6M LdqdV2WPsGW+azHhTfpvZL5jHAkPODM9Rx+JUFhCoUdNGWFQuuHXNn7/hMW6hVCjm2qK HhAq+0j+lmnIo1WCTYi2kfoIkBow33UsTX9stGwL6CLdB06/v4Cw1raDYlywe5rJOZs9 R9qw== X-Gm-Message-State: AOAM5321Kh2XfGgOjDe4S7VyR/LtHCNjiGRhNJdg0rz96nP5GFrSzBbC TRyxUXws+pOrLyPKeSAMhDyqsO7nRl8a+NDAlo4= X-Google-Smtp-Source: ABdhPJxbpUXBA/4OviBudfNIoRwiExpUXoc5M0M+8szGzAiXDC2idMYMrpfe7npoOuqaFggDGcUsQhfRW2pN8moltR0= X-Received: by 2002:a17:906:8301:b0:6e4:896d:59b1 with SMTP id j1-20020a170906830100b006e4896d59b1mr51902890ejx.396.1654010673759; Tue, 31 May 2022 08:24:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:640c:1fcc:b0:165:a4f7:ea4a with HTTP; Tue, 31 May 2022 08:24:33 -0700 (PDT) In-Reply-To: <165400680669.573549.5553646427767597793@wrigleys.postgresql.org> References: <165400680669.573549.5553646427767597793@wrigleys.postgresql.org> From: "David G. Johnston" Date: Tue, 31 May 2022 08:24:33 -0700 Message-ID: Subject: Re: CREATE EXTENSION not adding extension on second SCHEMA To: "gustavomilc@gmail.com" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000aa09a205e0505e58" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aa09a205e0505e58 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, May 31, 2022, PG Doc comments form 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 =3D public_test; > CREATE EXTENSION unaccent; > > and the response is: response: SQL Error [42710]: ERROR: extension > "unaccent" already exists > 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 multi= ple times explicitly - the self-describing error seems sufficient. David J. --000000000000aa09a205e0505e58 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, May 31, 2022, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the w= ebsite:

Page: https://www.postgresql.org/docs/14/sql-createexte= nsion.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 =3D public_test;
CREATE EXTENSION unaccent;

=C2=A0and the response is: response: SQL Error [42710]: ERROR: extension "unaccent" already exists


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.
<= br>
David J.

--000000000000aa09a205e0505e58--