Re: Add more sanity checks around callers of changeDependencyFor() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add more sanity checks around callers of changeDependencyFor()
Date
Msg-id 879484.1688496004@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add more sanity checks around callers of changeDependencyFor()  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Add more sanity checks around callers of changeDependencyFor()
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Hmm, shouldn't we disallow moving the function to another schema, if the
> function's schema was originally determined at extension creation time?
> I'm not sure we really want to allow moving objects of an extension to a
> different schema.

Why not?  I do not believe that an extension's objects are required
to all be in the same schema.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: suppressing useless wakeups in logical/worker.c
Next
From: Dmitry Dolgov
Date:
Subject: Re: pg_stat_statements and "IN" conditions