From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: log file rotate |
Date: | 2004-08-08 10:06:41 |
Message-ID: | 4115FB31.50602@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>Tom, you didn't like Andreas' idea of allowing the user to rotate the
>>log files on demand.
>
>
> Give me a use case that requires that, and is sufficiently interesting
> to justify even a marginal decrease in the reliability of the log
> process.
- Debugging some stuff, a distinct period of work, I'd like to start
with a fresh serverlog.
- When doing a backup, I'd like to continue with a fresh serverlog so I
can see what was happening since that point in time.
MSSQL calls this sp_cycle_errorlog.
I can't see even a marginal decrease of reliability, since the logger
already accepts SIGHUP, and will reevaluate postgresql.conf to set the
rotation_requested flag accordingly; I'm just asking for setting the
flag directly.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-08-08 10:15:01 | Re: log file rotate |
Previous Message | Erwin Moller | 2004-08-08 09:05:53 | Re: listing triggers |