Postgres Pro
Downloads
Home   >   mailing lists

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

From Kirk Wolak
Subject Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
Date
Msg-id CACLU5mSYB2Jw2yx1oo4vCAzVjz_m2C3KEWLrdaym7RJ+_k_-Ew@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)  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
Tree view


On Mon, Aug 29, 2022 at 1:55 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
The convention on these lists is to inline or bottom-post with trimming of excess reply quoting.

Thank you! 

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@

TBH, I created a simple example that showed the problem.  
[A Third Party Extension is what actually Broke]

Add these two references (below)??? (ie, because we updated how things work, please review this to make sure you have it correct)


Again, Thanks.  I see it clearly now!  Apologies! 

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
Next
From: Richard Guo
Date:
Subject: Re: foreign join error "variable not found in subplan target list"