Re: BUG #7890: wrong behaviour using pg_rotate_logfile() with parameter log_truncate_on_rotation = on

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: sari(dot)thiele(at)usit(dot)uio(dot)no
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7890: wrong behaviour using pg_rotate_logfile() with parameter log_truncate_on_rotation = on
Date: 2013-02-19 09:54:30
Message-ID: 22797.1361267670@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

sari(dot)thiele(at)usit(dot)uio(dot)no writes:
> ==> * this checks if the new file name is different from the old one.
> In my case it is still the same name and so the new log lines will be
> appended to the current file, not truncated like I expected.
> I think this is the wrong behaviour, what do you think?

No, that behavior is intentional. Otherwise you'd lose log data
earlier than the configuration specifies.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Rafael Martinez 2013-02-19 10:15:53 Re: BUG #7890: wrong behaviour using pg_rotate_logfile() with parameter log_truncate_on_rotation = on
Previous Message Peter Kroon 2013-02-19 08:50:25 Re: Nested xmlagg doesn't give a result 9.2.3