Re: Patch for pg_dump: Multiple -t options and new -T option - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject Re: Patch for pg_dump: Multiple -t options and new -T option
Date
Msg-id 40FCACEE.7000200@familyhealth.com.au
Whole thread Raw
In response to Re: Patch for pg_dump: Multiple -t options and new -T option  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch for pg_dump: Multiple -t options and new -T option  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-patches
>>Weeeeell, I guess I'm against it based on the rules of feature freeze,
>>even though it would be really useful for me :(
>
> It would have been a lot easier to approve it if it'd arrived on June 30
> rather than July 6 :-(.  However, I do believe that David originally
> submitted a slightly-too-late version of this in the previous release
> cycle, so maybe we could cut him a little slack and pretend this is a
> mistakenly-forgotten patch that we held over from 7.4.

Yes, the reason it would be nice for me is that currently if you want to
dump two specific, related tables from your db, there's no way to do it
with pg_dump within the one transactions (ie. maintaining integrity).  I
guess I'm in favour of -t -t but not -T depending on the complexity of
it.  I'll review the patch if you like.

Chris


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch for pg_dump: Multiple -t options and new -T option
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Patch for pg_dump: Multiple -t options and new -T option