Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 2AFB09FB6AA for ; Mon, 21 May 2007 11:47:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 56047-08 for ; Mon, 21 May 2007 11:46:59 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id C274B9FB48C for ; Mon, 21 May 2007 11:46:59 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id l4LEko17065021 for ; Mon, 21 May 2007 11:46:50 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id l4LEiMKF062997 for pgsql-admin@postgresql.org; Mon, 21 May 2007 11:44:22 -0300 (ADT) (envelope-from news) From: Chris Browne X-Newsgroups: pgsql.admin Subject: Re: Size of logfiles Date: Mon, 21 May 2007 10:44:17 -0400 Organization: cbbrowne Computing Inc Lines: 25 Message-ID: <60veemp77i.fsf@dba2.int.libertyrms.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux) Cancel-Lock: sha1:z/nURAmWVDhdBZ47ruYBuHPJIXU= To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/212 X-Sequence-Number: 25532 p.elmers@gmx.de (Peter Elmers) writes: > I have searched the web and am sorry to say that i found nothing > about the default behavior of the log files of postgres. > > Can anyone tell me when postgres will delete the logfiles or what > postgres automatically do with them? Can you be a bit more precise about that? There are the WAL log files; I expect you're not talking about that. I expect you're talking about the log files containing error messages, warnings, and such. PostgreSQL will not, itself, purge out such files; consider that you can configure it to distribute log information via syslog, which would push the logs into a mostly OS-managed area. You'll presumably want to figure out what YOU want your policy to be, and find suitable tools (lots available) to implement that policy... -- (reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc")) http://linuxfinances.info/info/linuxxian.html "We should start referring to processes which run in the background by their correct technical name:... paenguins." -- Kevin M Bealer