| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Patch for pg_dump: Multiple -t options and new -T option |
| Date: | 2004-07-20 06:47:21 |
| Message-ID: | 40FCBFF9.5090601@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> 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.
One problem with this patch is that there's no way to dump multiple
tables in different schemas. Does this matter? It's a bit
non-orthogonal...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB SD | 2004-07-20 07:31:56 | Re: localhost redux |
| Previous Message | Peter Eisentraut | 2004-07-20 05:59:43 | Re: pg_config |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-07-20 09:04:29 | Re: PITR COPY Failure (was Point in Time Recovery) |
| Previous Message | Peter Eisentraut | 2004-07-20 05:59:43 | Re: pg_config |