Re: BUG #19025: PostgreSQL log is not rotated
| От | Rahila Syed |
|---|---|
| Тема | Re: BUG #19025: PostgreSQL log is not rotated |
| Дата | |
| Msg-id | CAH2L28tgFTY=31T5EsyRPkC1YhVFER0GyHeN8qKb+1QGmgP5NA@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #19025: PostgreSQL log is not rotated (PG Bug reporting form <noreply@postgresql.org>) |
| Список | pgsql-bugs |
Hi,
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:
[PRO] $ ls -lh
total 16G
-rw-r--r-- 1 postgres postgres 16G Aug 19 12:16
postgresql-2025-07-12_001207.log
I have been searching any bug but I could not find it. Any ideas?
I haven't attempted to reproduce this yet. However, after reviewing the code
and the comments in the postgresql.conf file,
it appears that this is possible when rotation is triggered by file size and
log_truncation_on_rotation is 'on'
i.e logs may be appended to an existing file with the same name
instead of truncating the existing file.
This happens because truncation only occurs during time-based rotation.
log_truncation_on_rotation is 'on'
i.e logs may be appended to an existing file with the same name
instead of truncating the existing file.
This happens because truncation only occurs during time-based rotation.
Are you observing this behaviour when log_truncate_on_rotation is 'false' ?
Thank you,
Rahila Syed
В списке pgsql-bugs по дате отправления: