MIME-Version: 1.0
References: 
 <CAL5GnivMgBgRdY9YTLmAQKQa=TQVTRwghiGovK6Q6XxScdGOzg@mail.gmail.com>
 <CAPZdUVoT6VMQY4UeUhO_z4t8J6Re9qpUX3fuo+xH-Qc4xzbbkw@mail.gmail.com>
 <9B8D6FBB-9ECE-4A19-84D2-FF258412D552@elevated-dev.com>
In-Reply-To: <9B8D6FBB-9ECE-4A19-84D2-FF258412D552@elevated-dev.com>
From: Joe Tailleur <joe.tailleur@gmail.com>
Date: Fri, 30 May 2025 07:50:47 -0600
Message-ID: 
 <CAPZdUVrsOCDPYKy3HbO-g+zMo5a41r03f_O4KE=gN=KLePKN9A@mail.gmail.com>
Subject: Re: Seeking Suggestions for Best Practices: Archiving and Migrating
 Historical Data in PostgreSQL
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000002fb55c06365ab4d0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAPZdUVrsOCDPYKy3HbO-g%2BzMo5a41r03f_O4KE%3DgN%3DKLePKN9A%40mail.gmail.com>
Precedence: bulk

--0000000000002fb55c06365ab4d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Scott Ribe <scott_ribe@elevated-dev=
.com>
wrote:

> > On May 30, 2025, at 7:39=E2=80=AFAM, Joe Tailleur <joe.tailleur@gmail.c=
om>
> 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?

--0000000000002fb55c06365ab4d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It allows me to easily backup the schema (regardless of th=
e number of tables).=C2=A0 I can move several tables into that schema, and =
back up the schema.=C2=A0=C2=A0<div><br></div><div>Really just to help me o=
rganize my own processes.</div><div><br></div><div>Joe.<br><div><br></div><=
div><br></div></div></div><br><div class=3D"gmail_quote gmail_quote_contain=
er"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 30, 2025 at 7:45=E2=
=80=AFAM Scott Ribe &lt;<a href=3D"mailto:scott_ribe@elevated-dev.com">scot=
t_ribe@elevated-dev.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">&gt; On May 30, 2025, at 7:39=E2=80=AFAM, Joe Taille=
ur &lt;<a href=3D"mailto:joe.tailleur@gmail.com" target=3D"_blank">joe.tail=
leur@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Using table partitioning works well for me.=C2=A0 I detach and move th=
e 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 a=
rchive schema on the live database.<br>
<br>
What&#39;s the purpose of the archive schema?</blockquote></div>

--0000000000002fb55c06365ab4d0--