X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F1892D1B1DC for ; Wed, 9 Jun 2004 13:32:31 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 96446-10 for ; Wed, 9 Jun 2004 16:32:23 +0000 (GMT) Received: from mpls-qmqp-04.inet.qwest.net (mpls-qmqp-04.inet.qwest.net [63.231.195.115]) by svr1.postgresql.org (Postfix) with SMTP id 3D0CDD1B182 for ; Wed, 9 Jun 2004 13:32:21 -0300 (ADT) Received: (qmail 45993 invoked by uid 0); 9 Jun 2004 16:32:21 -0000 Received: from mpls-pop-04.inet.qwest.net (63.231.195.4) by mpls-qmqp-04.inet.qwest.net with QMQP; 9 Jun 2004 16:32:21 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-04.inet.qwest.net with SMTP; 9 Jun 2004 16:32:21 -0000 Date: Wed, 09 Jun 2004 10:32:56 -0600 Message-Id: <1086798776.23855.11.camel@localhost.localdomain> From: "Scott Marlowe" To: "David F. Skoll" Cc: pgsql-admin@postgresql.org Subject: Re: Dump only part of a DB In-Reply-To: References: Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/120 X-Sequence-Number: 13780 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...