public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Tailleur <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
Date: Fri, 30 May 2025 07:50:47 -0600
Message-ID: <CAPZdUVrsOCDPYKy3HbO-g+zMo5a41r03f_O4KE=gN=KLePKN9A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAL5GnivMgBgRdY9YTLmAQKQa=TQVTRwghiGovK6Q6XxScdGOzg@mail.gmail.com>
	<CAPZdUVoT6VMQY4UeUhO_z4t8J6Re9qpUX3fuo+xH-Qc4xzbbkw@mail.gmail.com>
	<[email protected]>

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 <[email protected]>
wrote:

> > On May 30, 2025, at 7:39 AM, Joe Tailleur <[email protected]>
> 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?

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL
  In-Reply-To: <CAPZdUVrsOCDPYKy3HbO-g+zMo5a41r03f_O4KE=gN=KLePKN9A@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox