| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: pg_dump function dumped after required for table definition |
| Date: | 2003-11-08 11:29:50 |
| Message-ID: | 20031108112950.GP24094@ns.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Reece Hart <reece(at)in-machina(dot)com> writes:
> > I have a hunch about why this happens and is rare. The pftype_id_lookup
> > function was created AFTER some of the tables using 'alter table set
> > default ...'. Thus, the function's OID is greater than the OID of the
> > tables which use them.
>
> Yeah, this is a well-known problem in pg_dump. We need to revise it to
> pay attention to the dependency information that's now available in
> pg_depend. At the moment your only alternative is to manually fix the
> reload order using pg_restore's features for controlling the reload
> order ... which features would never have existed in the first place
> if we'd had this problem nailed :-(
I'm guessing this isn't going to get fixed before 7.4 is released, eh?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-08 19:09:58 | Re: PostgreSQL 7.4RC1 crashes on Panther |
| Previous Message | Tom Lane | 2003-11-08 04:09:55 | Re: pg_dump function dumped after required for table definition |