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 1ka0SB-0000Bn-Q5 for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Nov 2020 17:50:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ka0SA-0007L9-Ns for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Nov 2020 17:50:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ka0SA-0007L1-I8 for pgsql-bugs@lists.postgresql.org; Tue, 03 Nov 2020 17:50:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ka0S8-0000xJ-FW; Tue, 03 Nov 2020 17:50:42 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0A3HoQXS957261; Tue, 3 Nov 2020 12:50:26 -0500 From: Tom Lane To: Miha Vrhovnik cc: Heikki Linnakangas , pgsql-bugs@lists.postgresql.org, PG Bug reporting form Subject: Re: BUG #16698: Create extension and search path In-reply-to: References: <16698-89213113705fc24a@postgresql.org> <918521.1604414169@sss.pgh.pa.us> Comments: In-reply-to Miha Vrhovnik message dated "Tue, 03 Nov 2020 18:10:09 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <957259.1604425826.1@sss.pgh.pa.us> Date: Tue, 03 Nov 2020 12:50:26 -0500 Message-ID: <957260.1604425826@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Miha Vrhovnik writes: > What are then extensions.. They live in some sort of limbo.. as they don't > behave like a natural extension of the database... As they behave > differently (because they "require" public shema in path if extensions are > created while in public schema ). You've got the wrong mental model. Extensions are containers, which may *contain* objects that live within schemas, but the extension itself does not. The key reason for doing it that way is that an extension might itself contain a schema, or more than one schema. regards, tom lane