| From: | Dennis Björklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Timothy Brier <briert(at)cepu(dot)ca>, Andrew Gould <andrewgould(at)yahoo(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Restoring a postgres database |
| Date: | 2003-07-09 08:48:46 |
| Message-ID: | Pine.LNX.4.44.0307091044430.1516-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 9 Jul 2003, Martijn van Oosterhout wrote:
> In fact, you could take the ultra pessimistic route and change pg_dump to
> dump in such a way that it will always work. That should be possible. Say
> in the order:
That is probably simplest way even if the dumps will be ugly. There might
also be some places in pg where you can't make the change needed to do it
like this. But pg have been getting a lot better in this respect with a
nice sql syntax to do things that you previously could only do by changing
system tables.
> I've never had a database with recursive dependancies so maybe I'm
> underestimating the problems here.
I've had it several times, and I don't think it's that uncommon.
--
/Dennis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2003-07-09 09:04:23 | Re: Restoring a postgres database |
| Previous Message | Richard Huxton | 2003-07-09 08:27:17 | Re: Native dataprovider on Windows |