Re: Weird quirk with pg_dump of complex types

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Weird quirk with pg_dump of complex types
Date: 2009-02-27 05:42:30
Message-ID: 49A77D46.5020104@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeff,

> In the general case though, for any object that refers to multiple other
> objects, I don't see any way around explicit schema qualification. I
> suppose it could be smart and say "foo_type is unique in my search path,
> so I don't need to schema-qualify it".

Yeah, but for most other objects "public" is also excluded as well as
pg_catalog. For CREATE TYPE, "public" is explicit.

> Have you considered working from the "custom" format rather than text?
> I'm not sure whether it solves your problem, but I think it provides the
> most information.

--Josh Berkus

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-02-27 05:50:14 Re: Weird quirk with pg_dump of complex types
Previous Message Jeff Davis 2009-02-27 05:19:55 Re: Weird quirk with pg_dump of complex types