From: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(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:22:25 |
Message-ID: | Pine.LNX.4.58.0407211018510.8830@shishi.roaringpenguin.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Wed, 21 Jul 2004, Bruce Momjian wrote:
> Even though I suggested it, I am afraid this is just too confusing an API.
How about this:
pg_dump -t t1 -- Dump table t1 in any schema
pg_dump -n s1 -- Dump all of schema s1
pg_dump -t t1 -n s1 -- Dump t1 in s1
pg_dump -t t1 -t t2 -n s1 -- Dump s1.t1 and s1.t2
pg_dump -t t1 -t t2 -n s1 -n s2 -- Dump s1.t1, s1.t2, s2.t1 and s2.t2
Basically, no "-t" option means dump all tables. No "-n" option
means dump all schemas. If any "-t" or "-n" options are present,
then we only dump the specified tables/schemas. We also probably
should not warn about missing tables, because it's likely that the
full cartesian product of schemas and tables won't exist.
And we nuke the -T and -N options.
Regards,
David.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2004-07-21 14:26:35 | Re: check point segments leakage ? |
Previous Message | Bruce Momjian | 2004-07-21 14:17:24 | Re: Patch for pg_dump: Multiple -t options and new -T option |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-07-21 14:30:23 | Re: logfile subprocess and Fancy File Functions |
Previous Message | Bruce Momjian | 2004-07-21 14:17:24 | Re: Patch for pg_dump: Multiple -t options and new -T option |