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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Weird quirk with pg_dump of complex types
Date: 2009-02-27 17:12:03
Message-ID: 49A81EE3.8050904@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeff Davis wrote:
> On Fri, 2009-02-27 at 01:24 -0500, Tom Lane wrote:
>> Are you entirely sure that they don't?
>
> Oh, you're right, of course:
>
> postgres=# create type public.mytype as (i int);
> CREATE TYPE
> postgres=# create type public.mytype2 as (j mytype);
> CREATE TYPE
>
> -- pg_dump output:
> CREATE TYPE mytype2 AS (
> j mytype
> );

Really?

Ok, I'll have to work up a reproduceable case, because I'm definitely
getting the "public" qualification in the create type.

--Josh

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Adam Flott 2009-02-27 17:26:05 BUG #4682: Control-\ segfaults psql
Previous Message Josh Berkus 2009-02-27 17:10:53 Re: Weird quirk with pg_dump of complex types