X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 20D2F32A0C8 for ; Sun, 17 Oct 2004 12:22:40 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13361-02 for ; Sun, 17 Oct 2004 11:22:25 +0000 (GMT) Received: from smtp.bltconsult.com (smtp.bltconsult.com [64.124.68.186]) by svr1.postgresql.org (Postfix) with ESMTP id BC98632A0AA for ; Sun, 17 Oct 2004 12:22:26 +0100 (BST) Received: from [138.89.132.102] (helo=LENNHOFF-PEXI.foo.bar) by 64.125.181.59 with asmtp (TLSv1:RC4-SHA:128) id 1CJ97B-0007Hh-00; Sun, 17 Oct 2004 07:22:17 -0400 Message-Id: <6.0.2.0.0.20041017071206.01e9f870@localhost> Date: Sun, 17 Oct 2004 07:22:16 -0400 To: Tom Lane From: Larry Lennhoff Subject: Re: Suppressing duplicate key error messages in Cc: pgsql-admin@postgresql.org In-Reply-To: <4602.1097985573@sss.pgh.pa.us> References: <6.0.2.0.0.20041016212538.01b2d7f8@localhost> <4602.1097985573@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/203 X-Sequence-Number: 15196 At 11:59 PM 10/16/2004, Tom Lane wrote: >Larry Lennhoff writes: > > Is there any way to suppress this message so that it won't appear in the > > log? I looked at the documentation and log_min_error_statement looked > > promising. I set it to panic, but the messages continue. What am I doing > > wrong? > >Did you remember to SIGHUP the postmaster after editing postgresql.conf? After the crash (caused by the log filling all available disk space) and restart I tried the following: pexicast_datran_sg=# show log_min_error_statement; log_min_error_statement ------------------------- panic (1 row) I did not change the value after the restart. I'm using pexicast 7.3.4. There are two databases in this instance, both have log_min_error_statement set to panic. Let me know if there is anything else I can tell you that might help. Larry