From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "developer(at)moregatebiotech(dot)com" <developer(at)moregatebiotech(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #17526: PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is assigned to a schema |
Date: | 2022-06-22 13:53:56 |
Message-ID: | CAKFQuwZPcWJ8FTQx_uqCoBuQGxyn5ML37iTe5igid1p++UqU7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tuesday, June 21, 2022, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17526
> Logged by: chris
> Email address: developer(at)moregatebiotech(dot)com
> PostgreSQL version: 14.4
> Operating system: Linux
> Description:
>
> PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is
> assigned to a schema.
>
>
Not a bug. Extension members are not dumped because the system expects
that a subsequent create extension command will create them. That is what
it means to be a member of the extension. Most users are not going to
execute the “alter extension add” command on there database as it doesn’t
really provide end-user useful functionality.
Extension assigned to a schema is not the correct model here. “Given
control of the schema” or “Schema becomes an implementation detail of the
extension” are.
I’ve been working on the docs in this area but focused on routines. I will
give this a look to see if additional clarity here is needed too.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-06-22 14:01:52 | Re: BUG #17526: PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is assigned to a schema |
Previous Message | PG Bug reporting form | 2022-06-22 05:34:58 | BUG #17528: ERROR: could not access status of transaction 1997627701 |