Re: Bug with specific-schema extensions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug with specific-schema extensions
Date: 2015-04-19 22:08:30
Message-ID: 6352.1429481310@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> CREATE EXTENSION creates the variant schema for me, but it leaves it
> behind when I drop the extension. I assume this is a bug and not by design?

No, it's intentional. If you want the schema to be considered part of the
extension, then create it within the extension.

We could have made this case fail, rather than auto-create the containing
schema. That would have been more consistent but probably less useful,
so we didn't.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-04-19 22:47:02 Re: Bug with specific-schema extensions
Previous Message Jim Nasby 2015-04-19 22:02:04 Allow SQL/plpgsql functions to accept record