From: slamp slamp <slackamp@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: pg_log directory
Date: Thu, 21 Aug 2008 09:25:07 -0400
Message-ID: <78926d250808210625m222d1fbcn229d238ab37e7507@mail.gmail.com> (raw)
In-Reply-To: <10859.1219282681@sss.pgh.pa.us>
References: <78926d250808201343x41e6840cma213c92572ec4268@mail.gmail.com>
<10859.1219282681@sss.pgh.pa.us>
On Wed, Aug 20, 2008 at 9:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That's just the server message log. While you could blow away the files
> without any ill effect, soon enough you'd have another 40GB. You need
> to either dial down the verbosity of your what-to-log settings, or
> modify the where-to-log settings to recycle log files more frequently,
> or both. In particular it sounds like you have set log_statement = all
> without, perhaps, understanding the consequences. Read the fine manual
> here:
> http://www.postgresql.org/docs/8.2/static/runtime-config-logging.html
>
> regards, tom lane
>
I am using the PGDG rpms. So it has the default logging configs. its
rotating daily but i have files there since 2007. is there a config
option to delete these files? i looked at the manual and i guess i
must be missing the option i want.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: slackamp@gmail.com
Subject: Re: pg_log directory
In-Reply-To: <78926d250808210625m222d1fbcn229d238ab37e7507@mail.gmail.com>
References: <78926d250808201343x41e6840cma213c92572ec4268@mail.gmail.com> <10859.1219282681@sss.pgh.pa.us> <78926d250808210625m222d1fbcn229d238ab37e7507@mail.gmail.com>
* 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