Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 57B66B5DC39 for ; Sat, 28 May 2011 10:59:20 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 62557-04 for ; Sat, 28 May 2011 13:59:13 +0000 (UTC) X-Greylist: delayed 00:09:23.738326 by SQLgrey-1.7.6 Received: from shrek.krogh.cc (2605ds1-ynoe.0.fullrate.dk [90.184.12.24]) by mail.postgresql.org (Postfix) with ESMTP id 24ABEB5DC38 for ; Sat, 28 May 2011 10:59:12 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id AFE151CDC5E; Sat, 28 May 2011 15:49:47 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I+ZWt368MTAl; Sat, 28 May 2011 15:49:44 +0200 (CEST) Received: from [90.184.13.151] (2605ds1-ynoe.2.fullrate.dk [90.184.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id C8A371CDC65; Sat, 28 May 2011 15:49:44 +0200 (CEST) Message-ID: <4DE0FD78.6080001@krogh.cc> Date: Sat, 28 May 2011 15:49:44 +0200 From: Jesper Krogh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Selva manickaraja , pgsql-admin@postgresql.org Subject: Re: PostgreSQL logs filling up file system due to duplicate key error References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201105/176 X-Sequence-Number: 37613 On 2011-05-28 15:19, Selva manickaraja wrote: > Please advise as to how we can solve this problem. We are worried that this > error could happen over the weekend and without our knowledge the db may > just show down again. Add in 2TB of space for the logs and instruct your monitoring system to tell you when it grows significantly. -- Jesper