| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump in 7.4 |
| Date: | 2002-11-13 05:50:43 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOKEILCEAA.chriskl@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> pg_dump already has rudimentary dependency tracking (one level
> deep); each
> item can have a list of oid's it depends on. You *could* patch it to add
> the types to the table dependencies.
>
> In the future I'd imagine we'll just dump the OIDs of all first level
> dependencies for each object, then at restore-time, process them in
> whatever order the user requests (defaulting to dependency-order).
Well, the problem is that you can add a new type and then add a column to a
really old table that uses that type - that causes pain. Lots of other
people have also reported the "view dumped before table it is based on"
problem.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2002-11-13 06:22:11 | performance regression, 7.2.3 -> 7.3b5 w/ VIEW |
| Previous Message | Philip Warner | 2002-11-13 05:40:52 | Re: pg_dump in 7.4 |