Re: db partial dumping with pg_dump

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>
Cc: "Rod Taylor" <rbt(at)zort(dot)ca>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: db partial dumping with pg_dump
Date: 2002-08-14 01:54:13
Message-ID: GNELIHDDFBOCMGBFGEFOIEKMCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2002-08-14 02:07:14 Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke
Previous Message Bruce Momjian 2002-08-14 01:38:15 Re: OOP real life example (was Re: Why is MySQL more