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

From David G. Johnston
Subject Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
Date
Msg-id CAKFQuwZu7WOeHNaiSbJRbEwT7MZ5YiyYv5j5Si2ZPu=HybT61Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)  (Kirk Wolak <wolakk@gmail.com>)
Responses Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
List 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@


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 by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Postgresql data erasure request - from Stefania Miravalle - request: ZN6NRXG3
Next
From: Kirk Wolak
Date:
Subject: Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)