From: Scott Marlowe <smarlowe@qwest.net>
To: David F. Skoll <dfs@roaringpenguin.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Dump only part of a DB
Date: Wed, 09 Jun 2004 10:32:56 -0600
Message-ID: <1086798776.23855.11.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0406091006180.6478@shishi.roaringpenguin.com>
References: <Pine.LNX.4.58.0406091006180.6478@shishi.roaringpenguin.com>
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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: smarlowe@qwest.net, dfs@roaringpenguin.com
Subject: Re: Dump only part of a DB
In-Reply-To: <1086798776.23855.11.camel@localhost.localdomain>
References: <Pine.LNX.4.58.0406091006180.6478@shishi.roaringpenguin.com> <1086798776.23855.11.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox