Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql

On Wed, Apr 9, 2014 at 10:15:28PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I see a filter on pg_catalog for pg_proc. Is there a reason there isn't
> > one for pg_extension?
>
> Extensions don't live in schemas.

That's what I thought too, but I see a schema file in pg_extensions:

test=> \d pg_extension
Table "pg_catalog.pg_extension"
Column | Type | Modifiers
----------------+---------+-----------
extname | name | not null
extowner | oid | not null
--> extnamespace | oid | not null
extrelocatable | boolean | not null
extversion | text |
extconfig | oid[] |
extcondition | text[] |
Indexes:
"pg_extension_name_index" UNIQUE, btree (extname)
"pg_extension_oid_index" UNIQUE, btree (oid)

SELECT extname, extnamespace, nspname
FROM pg_extension, pg_namespace
WHERE extnamespace = pg_namespace.oid;
extname | extnamespace | nspname
---------+--------------+------------
plpgsql | 11 | pg_catalog
(1 row)

Should we hard-code a pg_catalog plpgsql to be skipped in pg_dump?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +