| From: | shammat(at)gmx(dot)net |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Schedule pg_repack job with pg_cron |
| Date: | 2024-08-08 10:16:53 |
| Message-ID: | d6e421ef-5490-4e14-a278-aa6fe462377c@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-08-08 10:26:22 | Re: Schedule pg_repack job with pg_cron |
| Previous Message | Muhammad Imtiaz | 2024-08-08 08:43:34 | Re: Statement_timeout effect on replication user |