Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Joe Tailleur <joe(dot)tailleur(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Date: 2025-05-30 13:45:41
Message-ID: 9B8D6FBB-9ECE-4A19-84D2-FF258412D552@elevated-dev.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On May 30, 2025, at 7:39 AM, Joe Tailleur <joe(dot)tailleur(at)gmail(dot)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?

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message hubert depesz lubaczewski 2025-05-30 13:48:08 Re: pg_dump verbose start and stop times?
Previous Message Joe Tailleur 2025-05-30 13:39:53 Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL