pg_dump: a way to not dump indexes and other objects, or a way to not create them on restore, feature request?

From: Glen Parker <glenebob(at)nwlink(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_dump: a way to not dump indexes and other objects, or a way to not create them on restore, feature request?
Date: 2006-12-08 20:49:29
Message-ID: 4579CFD9.30509@nwlink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

Since PITR works well, my use of pg_dump has shifted. Rather than using
it as a backup tool, I now use it as a snapshotting tool. At the end of
each month we do an ASCII dump to keep around, so if we ever need to,
we can see the data as it was any number of months or years ago. Not a
backup at all, just a raw data archive.

These archives do not need to hold all our data, for example, system
logs would be useless later. There also is no reason to include
indexes. Ignoring extranious tables and indexes is a great way to keep
the archive small and keep the time to restore as low as possible.

So, it would be great if pg_dump could accept some sort of argument to
make it simply not dump certain types of objects. Indexes, views,
functions, etc.

Thx for considering :-)

-Glen Parker

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Glen Parker 2006-12-08 20:49:30 Marking indexes out of date (WAS: loading data, creating indexes, clustering, vacuum) feature request?
Previous Message Richard Troy 2006-12-08 20:40:19 Proposed ISO solution to Male/female