From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | WireSpot <wirespot(at)gmail(dot)com>, Roger Hand <RHand(at)kailea(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dump all except some tables? |
Date: | 2005-10-08 21:22:23 |
Message-ID: | 20051008212223.GB24701@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Oct 07, 2005 at 08:21:31PM -0500, Jim C. Nasby wrote:
> On Fri, Oct 07, 2005 at 02:07:47AM -0700, David Fetter wrote:
> > On Fri, Oct 07, 2005 at 11:47:26AM +0300, WireSpot wrote:
> > > But... will the resulting dump be consistent as far as foreign
> > > keys are concerned? Or will the current -t warning still apply
> > > (YMMV as to the consistency of the resulting dump)?
> >
> > I think the latter is better. This is solidly in the realm of
> > prying off cover plates, and the warning is already there :)
>
> I think it would be good to include an option that only does
> checking and doesn't actually try to dump anything. That would make
> it easier to ensure your config file is correct.
Could you flesh this out a bit? What would this option produce in the
(imho most common) case where dependencies weren't all taken care of?
Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2005-10-08 21:49:45 | Re: Oracle buys Innobase |
Previous Message | felix | 2005-10-08 21:11:54 | Re: Oracle buys Innobase |