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 2CA8332A099 for ; Sun, 17 Oct 2004 02:35:47 +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 11850-05 for ; Sun, 17 Oct 2004 01:35:34 +0000 (GMT) Received: from smtp.bltconsult.com (smtp.bltconsult.com [64.124.68.186]) by svr1.postgresql.org (Postfix) with ESMTP id 1FC1432A0A1 for ; Sun, 17 Oct 2004 02:35:36 +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 1CIzxQ-0006qo-00 for ; Sat, 16 Oct 2004 21:35:36 -0400 Message-Id: <6.0.2.0.0.20041016212538.01b2d7f8@localhost> Date: Sat, 16 Oct 2004 21:35:35 -0400 To: pgsql-admin@postgresql.org From: Larry Lennhoff Subject: Suppressing duplicate key error messages in postgres log? 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/197 X-Sequence-Number: 15190 Hi I have a postgres table which relies on a unique index to act as a semaphore to share a resource among many competing processes on several different servers. This table is hit multiple times per second. The postgres log is being filled by millions of messages of the sort ERROR: Cannot insert a duplicate key into unique index ... 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? Thanks in advance for any assistance Larry