From: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
---|---|
To: | Paul Brindusa <paulbrindusa88(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Log retention query |
Date: | 2025-01-28 12:19:28 |
Message-ID: | CAEG8a3+p5r3Mk4WPQKxTiExHNZXUfd3sTm1p9CpP9Fn3Jbf3JA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jan 28, 2025 at 5:57 PM Paul Brindusa <paulbrindusa88(at)gmail(dot)com> wrote:
>
> Good morning everyone,
>
> Before I get on with today's problem, I would like to say how much I appreciate this community and everything that you do for end users.
>
> In today's problem I would like to understand if the following lines in our config handle the log rotation for our clusters?
>
> log_checkpoints: on
> logging_collector: on
> log_truncate_on_rotation: on
> log_rotation_age: 1d
> log_rotation_size: 1GB
> log_error_verbosity: verbose
>
> I have been deleting the logs manually for the last month, since I am confused how the log collector rotates them.
>
> Am looking to delete logs older than 180 days. What are we doing wrong in the config?
I doubt Postgres can do this, but you can do this by adding a crontab
entry. e.g.
0 2 * * * find /path/to/logs -type f -mtime +180 -name "*.log" -exec rm {} \;
>
> --
> Kind Regards,
> Paul Brindusa
> paulbrindusa88(at)gmail(dot)com
>
--
Regards
Junwang Zhao
From | Date | Subject | |
---|---|---|---|
Next Message | Дмитрий | 2025-01-28 13:09:07 | Re[2]: FATAL: could not send data to WAL stream: lost synchronization with server: got message type "0", length 892351284 |
Previous Message | Jim Vanns | 2025-01-28 12:13:53 | Re: Parallel workers via functions? |