Re: pg_dumpall's output not totally usable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ojeannet(at)slb(dot)com
Cc: pgsql <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_dumpall's output not totally usable
Date: 2000-05-29 21:17:25
Message-ID: 7565.959635045@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Olivier Jeannet <jeannet(at)montrouge(dot)tt(dot)slb(dot)com> writes:
> The problem is that the output of pg_dumpall doesn't totally work, and I
> found that some statements are not in the proper order. So I edited the
> output, made some cuts and pastes, and was able to successfully restore the
> database. The few statements I had to put earlier in the output file are
> "CREATE FUNCTION" statements, like :
> CREATE FUNCTION "countadm_moduletable" (int4 ) RETURNS int4 AS 'SELECT
> count(*) FROM ADM_MODULETABLE WHERE MODULETABLEID = $1' LANGUAGE 'SQL';
> Does anyone know about this problem ?

Yeah, it's a known problem... pg_dump is pretty stupid about the order
it dumps stuff in. There's been talk of analyzing the dependencies
among all items in the database, but that looks *hard*. A 99% solution
is to dump things in order by OID, and that's what we'll probably do
sometime soon.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mitterwald, Holger 2000-05-30 11:30:16 Optimizer Bug?
Previous Message Olivier Jeannet 2000-05-29 19:46:40 pg_dumpall's output not totally usable