Re: Bug #787: Backup Files Output Constraints Before Functions
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: david(at)wheeler(dot)net, pgsql-bugs(at)postgresql(dot)org
- Subject: Re: Bug #787: Backup Files Output Constraints Before Functions
- Date: Fri, 27 Sep 2002 17:10:00 -0400
- Message-id: <7005.1033161000@sss.pgh.pa.us> <text/plain>
pgsql-bugs(at)postgresql(dot)org writes:
> Would it be possible for pg_dump to do the right thing here?
Not real soon :-(. It's possible that 7.4 pg_dump will be smart enough
to handle circular dependencies like this one. The current pg_dump
doesn't even know there is a problem, much less have a strategy for
coping.
I assume you can't simply create the try_it() function before the table
that uses it? (If you rewrote it as a plpgsql function, you probably
could do that, since the body of a PL function isn't checked when it's
defined. Perhaps this can serve as a workaround until pg_dump gets
smarter about dependencies.)
regards, tom lane
Home |
Main Index |
Thread Index