Re: HD is flooded by Error Log info

what i do is setup a cron job which runs daily or every second day, creates
a tar.gz and copies them to a seperate location, and then another cron job
which clears up archives more than one month old. That seems to be the way
to go, i don't think you will find a postgresql.conf parameter which does
that

On Nov 29, 2007 8:53 PM, Abraham, Danny <danny_abraham(at)bmc(dot)com> wrote:

> Hello
>
>
>
> Recently an application endless loop crashed the PG server.
>
> I am looking for the safest way to limit the growth of the all the files
> in the "pg_log" directory,
>
> While still maintain reasonable period of log.
>
>
>
> Any suggestions?
>
>
>
> Our current setup is:
>
>
>
>
> #---------------------------------------------------------------------------
>
> # ERROR REPORTING AND LOGGING
>
>
> #---------------------------------------------------------------------------
>
> redirect_stderr = on
>
> log_line_prefix = '%m'
>
> client_min_messages = error
>
> log_min_messages = error
>
>
>
> log_filename = 'CTMD-%d.log
>
> log_truncate_on_rotation = on
>
> log_rotation_age = 1d
>
> log_rotation_size = 10MB
>
>
>
>
>
> Thanks
>
>
>
>
>
> Danny Abraham
>
> BMC Software
>
> CTM&D Business Unit
>
> 972-52-4286-513
>
> danny_abraham(at)bmc(dot)com
>
>
>
>
>

--
Usama Munir Dar http://linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar