| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Kirk Wolak <wolakk(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX) |
| Date: | 2022-08-29 17:54:59 |
| Message-ID: | CAKFQuwZu7WOeHNaiSbJRbEwT7MZ5YiyYv5j5Si2ZPu=HybT61Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirk Wolak | 2022-08-29 18:24:14 | Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX) |
| Previous Message | Magnus Hagander | 2022-08-29 15:37:32 | Re: Postgresql data erasure request - from Stefania Miravalle - request: ZN6NRXG3 |