From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Major Problems with pg_dump |
Date: | 2005-01-11 17:31:18 |
Message-ID: | 20050111173118.GA32125@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Tom Lane wrote:
> =?iso-8859-1?Q?K=D6PFERL_Robert?= <robert(dot)koepferl(at)sonorys(dot)at> writes:
> >
> > 2. Dumping schema+data types and domains are dumped in the
> > wrong order.
> > Types don't get defined due to missing domains. Hmmm?
>
> However, 8.0 pg_dump should have solved the incorrect-dump-order
> problem. Could we see a specific example of #2 occurring with the 8.0
> dump?
I can duplicate this in 8.0.0rc5:
createdb test
psql -c "CREATE DOMAIN foo AS integer" test
psql -c "CREATE TYPE bar AS (x foo)" test
pg_dump test > test.sql
psql -c "DROP TYPE bar; DROP DOMAIN foo" test
psql -e test < test.sql
...
CREATE TYPE bar AS (
x foo
);
ERROR: type "foo" does not exist
ALTER TYPE public.bar OWNER TO postgres;
ERROR: type "public.bar" does not exist
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-11 17:57:16 | Re: Major Problems with pg_dump |
Previous Message | Keith Worthington | 2005-01-11 17:19:14 | Writing to dependent tables in a function |