From: | Philip Hallstrom <philip(at)adhesivemedia(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: dumping strategy |
Date: | 2001-06-01 02:05:19 |
Message-ID: | 20010531185751.U28853-100000@oddjob.adhesivemedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> writes:
> >> It's just
> >> for i in t1 t2 t3; do pg_dump -t$i mydb > $i.tbl; done
>
> > Although with a strategy like this, they're no guarantee that the
> > snapshot you get will be consistent. And if you're using refential
> > integrity it might not even restore properly.
>
> Good point. So who wants to tweak pg_dump to accept multiple -t
> switches? Seems like
>
> pg_dump -t foo -t bar -t baz dbname
>
> is a reasonably non-ambiguous syntax.
Not that I am anywhere close to being able to make thsese changes, but it
seems like it would be nice to have an option that says "dump all tables
except the ones specified". Kind of like grep's -V option...
maybe doing the two at the same time would be easier...
-philip
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Hoopman | 2001-06-01 06:39:06 | Re: PostgreSQL security concerns |
Previous Message | Doug McNaught | 2001-06-01 01:38:36 | Re: Disconnecting users for backup etc |