Re: Recommended Procedure for Archiving Table Data - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Recommended Procedure for Archiving Table Data
Date
Msg-id 4182A62C.8090301@commandprompt.com
Whole thread Raw
In response to Recommended Procedure for Archiving Table Data  ("Sally Ruggero" <sally.ruggero@northelectriccompany.com>)
List pgsql-general
Sally Ruggero wrote:

> I need advice on archiving data from our production database.
>
> Each night I would like to save and remove a day's data from two weeks
> ago, from all the tables. I know how to delete the data--though our
> schema does not specify cascaded deletes. However, I can't figure out
> how to save the desired data. I'd like to save it in SQL insert
> statement format, but I can't see how to get the data out. If I use
> psql to create a temp table with the old data in it, then the table
> disappears when I exit psql and I can't dump it with pg_dump. If I
> make a new table and put the data in it, then when I dump it with
> pg_dump, all the insert statements have the new table name rather than
> the original table name. I'm sure there's a good solution for this
> standard problem. Does anyone have a suggestion?

Create a temporary table from a query definition...
BEGIN;
create temp table archive_table as select * from foo where date between ....
delete from foo where date between ...
copy foo to '/tmp/archive.copy'
commit;

You probably want to at least do some basic checks on the data like row
counts
but that will archive out the data.

You could also just create an archival schema that you could push stuff to.

Sincerely,

Joshua D. Drake



>
> Thanks,
> Sally



--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Attachment

pgsql-general by date:

Previous
From: "Sally Ruggero"
Date:
Subject: Recommended Procedure for Archiving Table Data
Next
From: Chris Browne
Date:
Subject: Re: Reasoning behind process instead of thread based