From: Laurenz Albe <laurenz.albe@cybertec.at>
To: SOzcn <selahattinozcnma@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Log Rotation
Date: Tue, 12 Dec 2023 23:48:33 +0100
Message-ID: <1f8c46da652b1d24e4d38d73682318e1d8d07f51.camel@cybertec.at> (raw)
In-Reply-To: <CAJyV5Aa3rJ11kETeDZUXLktjbm0r8nugjYE4yR=iUay58W2hXA@mail.gmail.com>
References: <CAJyV5AbCRUdGE0TbdXJ02wfRGwq7uLd1UmmE-GE8nqqUf4U-Zw@mail.gmail.com>
<2444342.1702397882@sss.pgh.pa.us>
<CAJyV5Aa3rJ11kETeDZUXLktjbm0r8nugjYE4yR=iUay58W2hXA@mail.gmail.com>
On Tue, 2023-12-12 at 19:25 +0300, SOzcn wrote:
> On the top you can see the parameters, I already set the parameters as
> you said. But the truncate didn't work for daily.
Again: PostgreSQL will only truncate a file if, during log rotation,
it starts writing to a file that already exists.
It does not take care about old, closed log files.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, selahattinozcnma@gmail.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: Log Rotation
In-Reply-To: <1f8c46da652b1d24e4d38d73682318e1d8d07f51.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox