Re: Patch for pg_dump: Multiple -t options and new -T

From: "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for pg_dump: Multiple -t options and new -T
Date: 2004-07-21 14:59:28
Message-ID: Pine.LNX.4.58.0407211056450.8830@shishi.roaringpenguin.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Wed, 21 Jul 2004, Tom Lane wrote:

> pg_dump -t s1.t1 -t s2.t2 -- Dump s1.t1 and s2.t2

That's a good idea, but then it's questionable whether we need the -n
switch at all. It might be simpler to extend the -t switch to
accept:

pg-dump -t 's1.*'

rather than using a -n switch. Of course, that breaks
backward-compatibility.

Regards,

David.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-21 15:09:17 Re: Patch for pg_dump: Multiple -t options and new -T option
Previous Message Tom Lane 2004-07-21 14:53:49 Re: [HACKERS] Point in Time Recovery

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-07-21 15:09:17 Re: Patch for pg_dump: Multiple -t options and new -T option
Previous Message Tom Lane 2004-07-21 14:53:49 Re: [HACKERS] Point in Time Recovery