Re: Weird quirk with pg_dump of complex types - Mailing list pgsql-bugs

From Jeff Davis
Subject Re: Weird quirk with pg_dump of complex types
Date
Msg-id 1235692241.14110.3.camel@dell.linuxdev.us.dell.com
Whole thread Raw
In response to Weird quirk with pg_dump of complex types  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Weird quirk with pg_dump of complex types  (Josh Berkus <josh@agliodbs.com>)
List pgsql-bugs
On Thu, 2009-02-26 at 15:25 -0800, Josh Berkus wrote:
> 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.
>

Strange. However, I don't think setting the search path will suffice,
because the different types could come from different schemas in a way
that makes it impossible.

Functions are similar, actually. The argument list needs to specify
schema paths as well, if it's not in some expected place (I think it
does so for all schemas other than pg_catalog).

Regards,
    Jeff Davis

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: Weird quirk with pg_dump of complex types
Next
From: Josh Berkus
Date:
Subject: Re: Weird quirk with pg_dump of complex types