| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Dump/Restore ordering problem? |
| Date: | 2004-01-12 22:36:38 |
| Message-ID: | 5586.1073946998@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"D. Dante Lorenso" <dante(at)lorenso(dot)com> writes:
> Is there something I need to do to make the
> dependency ordering work smarter during a dump/restore?
This is fixed in CVS tip's pg_dump. You could probably get away with
using the development pg_dump with a 7.4 server --- I don't think we've
introduced any incompatibilities yet. If you're running something older
than 7.4, though, you'll have to keep hacking the dump order.
pg_restore has some options for fixing the order at reload time, which
would be your best bet if the schema is large.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Satrapa | 2004-01-12 22:40:37 | Re: Drawbacks of using BYTEA for PK? |
| Previous Message | Tom Lane | 2004-01-12 22:31:26 | Re: Vacuum Error |