| From: | "Scott Marlowe" <smarlowe(at)qwest(dot)net> |
|---|---|
| To: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Dump only part of a DB |
| Date: | 2004-06-09 16:32:56 |
| Message-ID: | 1086798776.23855.11.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2004-06-09 at 08:09, David F. Skoll wrote:
> Hi,
>
> pg_dump can be used to dump an entire database, or just a single
> table. Is there a way to make a consistent dump of more than one
> table, but less than all of the tables in the database? Doing a bunch
> of single-table pg_dumps isn't really an option, because some tables
> may change during the dumps, leading to constraint violations if we
> try to restore them.
>
> Rationale: We have an application that makes a nightly dump of its
> database. There's one particular table that tends to be large, but happily
> it's not critical if it's lost -- no real need to back it up. So we'd
> like to back up everything except that one large, non-critical table.
If you put the application's data into a specific schema, then you can
dump just that schema with the -n switch...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2004-06-09 16:38:19 | Re: PostgreSQL Performance |
| Previous Message | Tom Lane | 2004-06-09 14:48:09 | Re: PostgreSQL 7.4.2 on SunOS 4.1.4 |