From: | "Arnold, Sandra" <ArnoldS(at)osti(dot)gov> |
---|---|
To: | 'John R Pierce' <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Limiting records in pg_dump |
Date: | 2009-07-31 18:31:46 |
Message-ID: | 54E5385D47A89542BC678F5426799F39043DF76ED3@OSTIEX01.osti.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for that suggestion. Since I have a schema on the database, I could create the view on my schema or even a table with the same name with just the records that I want to copy to the other database. I had thought about the table but not necessary the view.
We are just in the process of looking at PostgreSQL as a solution to replace Oracle. Those high Maintenance and Support cost have made it necessary to find a replacement for Oracle.
-----Original Message-----
From: John R Pierce [mailto:pierce(at)hogranch(dot)com]
Sent: Friday, July 31, 2009 1:59 PM
To: Arnold, Sandra; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Limiting records in pg_dump
Arnold, Sandra wrote:
> Is there a way to just dump records equal to a specific value using
> pg_dump? In Oracle, you can export data and use a WHERE clause and
> only pull a range of data. We currently use this in Oracle to load
> data sets in our Development database. As we move to PostgreSQL we
> will be wanting to do the same thing. If we cannot do it using the
> pg_dump command, I will need to find a work around.
you could create an alternate schema in your DB with VIEW's to your
database table(s) that filter it according to your requirements, then
pg_dump -n schemaname ....
From | Date | Subject | |
---|---|---|---|
Next Message | Alan McKay | 2009-07-31 18:32:21 | change ownership on all tables |
Previous Message | John R Pierce | 2009-07-31 17:59:24 | Re: Limiting records in pg_dump |