From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | jose(dot)morcillo(dot)valenciano(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #19025: PostgreSQL log is not rotated |
Date: | 2025-08-20 11:19:25 |
Message-ID: | aKWvPeFfTMP-4d7Z@depesz.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 19, 2025 at 10:21:28AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19025
> Logged by: José Antonio Morcillo Valenciano
> Email address: jose(dot)morcillo(dot)valenciano(at)gmail(dot)com
> PostgreSQL version: 16.2
> Operating system: Red Hat Enterpr Linux 5.14.0-427.35.1.el9_4.x86_64
> Description:
>
> Hi folks!
>
> We have configured our log rotating policy as follows:
>
> logging_collector = on
> log_destination = 'stderr'
> log_directory = '/postgresql/16/log/cpdm-cluster86'
> log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log'
> log_rotation_age = 1d
> log_rotation_size = 250MB
> log_truncate_on_rotation = on
>
> But the log is 16GB and no rotation has happened:
Please connect to the db, and check what are values of these settings
*inside* db.
You can do it by doing:
SELECT
name,
setting,
source,
sourcefile,
sourceline
FROM
pg_settings
WHERE
name IN = ANY ('{logging_collector,log_destination,log_directory,log_filename,log_rotation_age,log_rotation_size,log_truncate_on_rotation}'::text[]);
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2025-08-20 11:21:07 | Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache |
Previous Message | shveta malik | 2025-08-20 10:16:30 | Re: Unexpected Standby Shutdown on sync_replication_slots change |