From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump additional options for performance |
Date: | 2008-02-06 16:31:56 |
Message-ID: | 47A9E0FC.5000601@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Wed, 2008-02-06 at 16:41 +0100, Magnus Hagander wrote:
>
> I don't think the two syntaxes compete. I want to be able to say
> "everything before", "data" and "everything after" without having to
> remember to specify --what=tables,views,sequences,kitchensink etc.
> Especially since you probably won't notice you've missed out an object
> type (e.g. sequences) until you try to run an application. Too late!
Is this not a job for the -l / -L mode of pg_restore, but ported to pg_dump?
With a bit of tweaking ti the format you could do something like:
pg_dump -l mydb | grep BEFORE > obj_list.txt
pg_dump -L obj_list.txt mydb > mydb.before.schema
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-02-06 16:36:14 | Re: PostgreSQL 8.4 development plan |
Previous Message | Andrew Dunstan | 2008-02-06 16:24:35 | Re: PostgreSQL 8.4 development plan |