Re: Schedule pg_repack job with pg_cron - Mailing list pgsql-admin

From shammat@gmx.net
Subject Re: Schedule pg_repack job with pg_cron
Date
Msg-id d6e421ef-5490-4e14-a278-aa6fe462377c@gmx.net
Whole thread Raw
In response to Re: Schedule pg_repack job with pg_cron  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Schedule pg_repack job with pg_cron
List pgsql-admin
Ron Johnson schrieb am 07.08.2024 um 21:39:
> Part of a properly-maintained system is *regularly* archive/purging
> (whether that be dropping date-based partitions, or deleting old
> data from unpartitioned tables or tables partitioned by something
> other than a date).
>
> For example, I gave a list of tables (all intertwined via FK
> constraints) to the application support people, and they returned
> the list stating how many weeks or months of data to retain in each
> table.  Every Saturday night a cron job goes through and deletes the
> old data from, and then "manually" vacuum-analyzes them.


If the application will then insert new data after the cleanup, Postgres
will re-use the free space that the delete "created". So depending
on the speed of inserts, you might not really gain that much.




pgsql-admin by date:

Previous
From: Muhammad Imtiaz
Date:
Subject: Re: Statement_timeout effect on replication user
Next
From: Ron Johnson
Date:
Subject: Re: Schedule pg_repack job with pg_cron