From: Tom Lane <tgl@sss.pgh.pa.us>
To: Miha Vrhovnik <miha.vrhovnik@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #16698: Create extension and search path
Date: Tue, 03 Nov 2020 12:50:26 -0500
Message-ID: <957260.1604425826@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAjGE4roRjCHnn1mOccGB+dsjqJT2JxdOkCuVAh6Teo=91ZXWA@mail.gmail.com>
References: <16698-89213113705fc24a@postgresql.org>
<b2e2d2a5-caa2-7141-dee1-ba7cfcb74fd8@iki.fi>
<CAAjGE4oD9W3BG1aZ90SVd3b2hUSC5bM3XL4_noyeHwH0gUycZg@mail.gmail.com>
<918521.1604414169@sss.pgh.pa.us>
<CAAjGE4roRjCHnn1mOccGB+dsjqJT2JxdOkCuVAh6Teo=91ZXWA@mail.gmail.com>
Miha Vrhovnik <miha.vrhovnik@gmail.com> 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
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, miha.vrhovnik@gmail.com, hlinnaka@iki.fi, noreply@postgresql.org
Subject: Re: BUG #16698: Create extension and search path
In-Reply-To: <957260.1604425826@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox