Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
Дата
Msg-id CAKFQuwZu7WOeHNaiSbJRbEwT7MZ5YiyYv5j5Si2ZPu=HybT61Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)  (Kirk Wolak <wolakk@gmail.com>)
Ответы Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)  (Kirk Wolak <wolakk@gmail.com>)
Список pgsql-bugs
Дерево обсуждения
The convention on these lists is to inline or bottom-post with trimming of excess reply quoting.

On Mon, Aug 29, 2022 at 9:00 AM Kirk Wolak <wolakk@gmail.com> wrote: 
OR I am clearly doing things incorrectly.

You seem to be trying to hard-code the schema instead of letting the extension creation infrastructure handle that for you by delegating to the instance-specific reference @extschema@

https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION
https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-EXAMPLE

Even if you want to force a fixed schema you need to do it in the way described in the documentation.

David J.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Postgresql data erasure request - from Stefania Miravalle - request: ZN6NRXG3
Следующее
От: Kirk Wolak
Дата:
Сообщение: Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)