From: | Duncan Sargeant <dunc-postgres(at)rcpt(dot)to> |
---|---|
To: | Andrew McMillan <andrew(at)catalyst(dot)net(dot)nz> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: table move across databases |
Date: | 2002-07-25 03:57:42 |
Message-ID: | 20020725035741.GD22945@circe.rcpt.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Andrew McMillan wrote on Tue July 23, at 20:49 +1200:
> What I do myself for a similar situation, is to:
>
> This gives me a separate table with the old records. I can then use
> pg_dump ... -t archive_YYMMDD to dump that table out, and finally drop
> it.
>
> I do this before the table gets too much in it, so that vacuuming it out
> is less of an issue, although that will be much less problematic when I
> upgrade to 7.2 in the next month or so.
>
> I hope this gives you some ideas,
Thanks Andrew, it does. Although it does frustrate me not being able
to keep the archived data online without copying all the data twice. At
least I get a backup out of one of them.
,dunc
From | Date | Subject | |
---|---|---|---|
Next Message | denis | 2002-07-25 07:17:11 | Trigger question |
Previous Message | Ron Johnson | 2002-07-25 00:07:52 | Re: extract text and store in postgres |