Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id E98BDF765A for ; Wed, 11 Apr 2012 20:51:39 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SI7K5-00029K-Rb for pgsql-admin@postgresql.org; Wed, 11 Apr 2012 23:51:39 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q3BNpOKU015456; Wed, 11 Apr 2012 19:51:24 -0400 (EDT) To: Wells Oliver cc: pgsql-admin@postgresql.org Subject: Re: Definitive logrotate solution? In-reply-to: References: <12916.1334185397@sss.pgh.pa.us> Comments: In-reply-to Wells Oliver message dated "Wed, 11 Apr 2012 16:40:28 -0700" Date: Wed, 11 Apr 2012 19:51:24 -0400 Message-ID: <15455.1334188284@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/64 X-Sequence-Number: 39400 Wells Oliver writes: > How do you ensure you're not keeping logs from 35+ days ago, or whatever? > Just a find -mtime +10 -exec rm {}\; kind of thing? Well, that depends on what you want to do. I like to choose the log file names so that they'll automatically be reused once a week or month. regards, tom lane