Re: log_filename_prefix --> log_filename + strftime()

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: log_filename_prefix --> log_filename + strftime()
Date: 2004-08-29 12:38:36
Message-ID: 4131CE4C.2060202@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On 8/29/2004 5:12 AM, Andreas Pflug wrote:

> Tom Lane wrote:
>> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>>
>>>Tom Lane wrote:
>>>
>>>>I can see the value of not needing any cron daemon to remove old logs.
>>
>>
>>>No other logs on your system to purge?
>>
>>
>> The DBA isn't necessarily also root.
>
> Interesting this argument comes from you.. :-)
>
> Tasks like purging old log files is certainly not a job that needs to be
> implemented in the backend; instead, an external database maintenance
> agent should do that.

You must have misunderstood something here. The proposal doesn't
implement any logfile purging feature, but allows to setup a
configuration that automatically overwrites files in a rotating manner,
if the DBA so desires. I can't see how you're jumping to logfile purging
from that.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message pgsql 2004-08-29 13:24:59 Re: Contrib -- PostgreSQL shared variables
Previous Message Jan Wieck 2004-08-29 12:19:50 Re: log_filename_prefix --> log_filename + strftime()