Postgres Pro
Downloads
Home   >   mailing lists

Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL - Mailing list pgsql-admin

From Joe Tailleur
Subject Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Date
Msg-id CAPZdUVrsOCDPYKy3HbO-g+zMo5a41r03f_O4KE=gN=KLePKN9A@mail.gmail.com
Whole thread Raw
In response to Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
Tree view
It allows me to easily backup the schema (regardless of the number of tables).  I can move several tables into that schema, and back up the schema.  

Really just to help me organize my own processes.

Joe.



On Fri, May 30, 2025 at 7:45 AM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> On May 30, 2025, at 7:39 AM, Joe Tailleur <joe.tailleur@gmail.com> wrote:
>
> Using table partitioning works well for me.  I detach and move the partition to an archive schema; which I can then backup and restore into a separate database, and once that is complete, remove the table from the archive schema on the live database.

What's the purpose of the archive schema?

pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Next
From: Ron Johnson
Date:
Subject: Re: pg_dump verbose start and stop times?