From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Ordering of pg_dump output |
Date: | 2000-02-08 16:14:46 |
Message-ID: | 2013.950026486@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> creation of index works now. But what about pg_dump ?
> I still have to edit manually dump file.
> look to excerption from dump file:
> CREATE TABLE "applicant" (
> "candx" int2 DEFAULT next_applicant() NOT NULL,
> "candidate" text,
> "candt" int2,
> "img" text
> );
> This fails because function next_applicant dumps later !
Yeah, it's a known bug. We can't just dump the functions first,
though, can we? I'm not sure how carefully function definitions
get examined by CREATE FUNCTION.
The simplest real solution I've heard so far is to dump database objects
in order by OID rather than doing it strictly by type.
Is anyone working on this, or does anyone want to? I haven't looked at
pg_dump in a while, but I know some other folks have been hacking it
recently.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 2000-02-08 16:22:43 | Re: [HACKERS] New Globe |
Previous Message | Bruce Momjian | 2000-02-08 16:02:01 | Re: [HACKERS] psql and libpq fixes |