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

From: Joe Tailleur <joe(dot)tailleur(at)gmail(dot)com>
To: 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:50:47
Message-ID: CAPZdUVrsOCDPYKy3HbO-g+zMo5a41r03f_O4KE=gN=KLePKN9A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)elevated-dev(dot)com>
wrote:

> > 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 Scott Ribe 2025-05-30 13:56:31 Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Previous Message hubert depesz lubaczewski 2025-05-30 13:48:08 Re: pg_dump verbose start and stop times?