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

From: Ilya Kosmodemiansky <ik(at)dataegret(dot)com>
To: Motog Plus <mplus7535(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 10:56:36
Message-ID: CAG95seU7jONxDvMnTkC23pgFPGmO=zG266CR1ZThjrbvvtz8VA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Ramzy,

On Fri, May 30, 2025 at 9:51 AM Motog Plus <mplus7535(at)gmail(dot)com> wrote:
> We’d like to understand:
> - What approaches have worked well for you in practice?

It really depends on your requirements. What volumes of data you store
and intend to archive? Are your tables partitioned, or is partitioning
at least an option for you? Would it be a rear operation (really once
a year) or you need to do it regularly

Best regards,
Ilya Kosmodemiansky
CEO, Founder

Data Egret GmbH
Your remote PostgreSQL DBA team
T.: +49 6821 919 3297
ik(at)dataegret(dot)com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ron Johnson 2025-05-30 12:39:43 Re: pg_dump verbose start and stop times?
Previous Message Holger Jakobs 2025-05-30 10:44:04 Re: Seeking Suggestions for Best Practices: Archiving and Migrating Historical Data in PostgreSQL