From: | Paul Brindusa <paulbrindusa88(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Log retention query |
Date: | 2025-02-02 12:12:07 |
Message-ID: | be48b84f-ffcb-4be7-9489-3686ad74b5bd@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Good afternoon Peter,
I had the exact same query as Junwang proposed.
Was mega upset that I could not get the cronjobs to work, and from what
I can tell from @Laurenz's response above we have the names of the logs
customised to posgtres-%d-%m-%y. Removing the logs after a week or month
does not since our retention policy is 6 months.
The cron job was set from root and it did not remove the logs/
On 02/02/2025 08:26, Peter J. Holzer wrote:
> On 2025-01-28 13:40:42 +0000, Paul Brindusa wrote:
>> @Junwang apologies, I should have mentioned that we've tried setting up a
>> crontab and it has not worked.
> Then you have a cron problem and not a postgresql problem.
>
> What that problem is is impossible to say with the information you have
> given us. What was the exact crontab entry, and what did it do? (When
> describing a problem, always use positives, not negatives. "it did not
> work" is particularly useless, since there are a gazillion ways in which
> something could not do what you expected.)
>
>> Have you got something similar working?
> Yes. Cleaning up stuff is probably one of the most frequent uses of
> cron.
>
> hp
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shaheed Haque | 2025-02-02 13:58:18 | Idempotent CREATE SUBSCRIPTION and DROP SUBSCRIPTION pair |
Previous Message | Peter J. Holzer | 2025-02-02 08:26:18 | Re: Log retention query |