All,
This is not so much a bug as a weird inconsistency, which ought to go on
a list somewhere so that it gets cleaned up the next time someone
overhauls pg_dump:
Summary: CREATE TYPE uses explicit schemas
Versions Tested: 8.2.9, 8.3.5
Platform: Linux
Description of Issue:
When doing pg_dump in text mode, complext types will be dumped like this:
CREATE TYPE complex_foo (
var INT,
gar TEXT,
natch public.foo_type
);
That is, a custom type in a complex type declaration is explicitly
schema-qualified, even when the schema in question is in the default
schema_path. This is inconsistent with all other database objects,
which use "SET search_path" to qualify the correct schemas.
This is only a real problem in that it may interfere with backup and/or
schema comparison automation (like I'm trying to write right now).
--Josh Berkus
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
