From: | Rod Taylor <rbt(at)zort(dot)ca> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: db partial dumping with pg_dump |
Date: | 2002-08-13 12:00:09 |
Message-ID: | 1029240009.74400.9.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2002-08-13 at 07:49, Oleg Bartunov wrote:
> We have a patch for pg_dump which adds a possibility to dump
> a part of table, for example:
>
> dump Top.Science.Astronomy heirarchy from dmoz catalog
>
> pg_dump -d -t dmoz -w "select * from dmoz where path <@ 'Top.Science.Astronomy'" dmoz
>
> We found it's very useful. We'd like to extend it to use also with COPY
> but it has no support for select (of course it will works only for
> special case when ALL columns retrieved).
>
> The question is: Is't worth to submit patch for pg_dump and look into
> copy code ?
I've been asked by co-workers for information on how to do this type of
thing. They do partial table dumps to a development system for the
purpose of finding / eliminating bugs.
That said, it may be smart to make the 'select * from <table>' part
yourself, and let the user supply a where clause.
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2002-08-13 12:18:21 | Re: [GENERAL] Linux Largefile Support In Postgresql RPMS |
Previous Message | Oleg Bartunov | 2002-08-13 11:49:39 | db partial dumping with pg_dump |