Re: Weird quirk with pg_dump of complex types

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Weird quirk with pg_dump of complex types
Date: 2009-02-27 05:50:14
Message-ID: 12520.1235713814@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 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
> );

You didn't say which schema "complex_foo" is in?

> 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.

There is no such thing as a default search path for pg_dump's purposes.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Davis 2009-02-27 06:15:14 Re: Weird quirk with pg_dump of complex types
Previous Message Josh Berkus 2009-02-27 05:42:30 Re: Weird quirk with pg_dump of complex types