Re: Additive backup and restore?

From: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Additive backup and restore?
Date: 2023-05-08 11:02:42
Message-ID: 66A8BBE2-D6FF-4ABC-B04B-67CB2367733A@a-kretschmer.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Consider table partitioning. You can detach, save and delete partitions, and you can restore and attach partitions.

On 8 May 2023 12:24:06 CEST, Age Apache <age(dot)apache(at)gmail(dot)com> wrote:
>I am designing a database for a web application. In the near future I will
>require past data for Audit, Security and Analysis purpose. But storing all
>that data will increase the database size. What are some well known
>approaches to archiving data for later use without increasing the database
>size?
>
>One approach I am thinking of is compressed additive backup and restore
>i.e. copy the rows of the tables that will be required later and store them
>in a compressed form, and then delete those rows from the table. And when
>the data is required then restore them from the backup files in an additive
>way.
>
>Is there an easy way to achieve this, say via pg_dump?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kent Tong 2023-05-08 12:29:09 huge discrepancy between EXPLAIN cost and actual time (but the table has just been ANALYZED)
Previous Message shveta malik 2023-05-08 11:01:20 Re: Support logical replication of DDLs