Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group