Re: db partial dumping with pg_dump - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: db partial dumping with pg_dump
Date
Msg-id GNELIHDDFBOCMGBFGEFOIEKMCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: db partial dumping with pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: db partial dumping with pg_dump  (Scott Shattuck <ss@technicalpursuit.com>)
Re: db partial dumping with pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I'm finding it hard to visualize situations where I'd want the extra
> baggage of pg_dump for something like this.  If I want the schema at
> all, I'll probably want it separate from the data so that I can hack
> the schema conveniently --- so I'd want to do a "pg_dump -s -t table"
> and then do the selective copying separately.

Tell you what I'd kill for:

pg_dump -t users_\* db > users.sql

Sort of thing.

Chris



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: OOP real life example (was Re: Why is MySQL more
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke