Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43717=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Ycjni-0004Oq-NV
 for pgsql-admin@arkaria.postgresql.org; Tue, 31 Mar 2015 00:13:02 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43717=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Ycjni-0007wi-11
 for pgsql-admin@arkaria.postgresql.org; Tue, 31 Mar 2015 00:13:02 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <scott@journyx.com>) id 1Ycjnf-0007wP-RW
 for pgsql-admin@postgresql.org; Tue, 31 Mar 2015 00:12:59 +0000
Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com)
 by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <scott@journyx.com>) id 1YcjnZ-0008TS-0U
 for pgsql-admin@postgresql.org; Tue, 31 Mar 2015 00:12:57 +0000
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id 43AF3301F8F;
 Mon, 30 Mar 2015 19:12:49 -0500 (CDT)
Received: from mail.int.journyx.com ([127.0.0.1])
 by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id 84AfgFIneANt; Mon, 30 Mar 2015 19:12:49 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id 0A060301F92;
 Mon, 30 Mar 2015 19:12:49 -0500 (CDT)
X-Amavis-Modified: Mail body modified (using disclaimer) -
 mail.int.journyx.com
X-Virus-Scanned: amavisd-new at mail.int.journyx.com
Received: from mail.int.journyx.com ([127.0.0.1])
 by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id 7Qlg6I3mZt6p; Mon, 30 Mar 2015 19:12:48 -0500 (CDT)
Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5])
 by mail.int.journyx.com (Postfix) with ESMTP id C0871301F8F;
 Mon, 30 Mar 2015 19:12:48 -0500 (CDT)
MIME-Version: 1.0
X-Mailer: CloudMagic
X-Mailer: Zimbra 8.6.0_GA_1153 (MobileSync - CloudMagic)
X-Cm-Message-Id: 
 142776076773223592443d373fb8ea0eb7f613e8a190b2b85519e67fb2cfb1680813879
In-Reply-To: <4BFDA821-C2D3-4614-A66F-FF0D9FDEE5EB@elevated-dev.com>
References: <33A4D5087BF0D44DA69C5EEF666BC1D74263DD2C@usprmbp01c>
To: "Scott Ribe" <scott_ribe@elevated-dev.com>
Cc: "Rossi, Maria" <maria.rossi@us.pgds.com>, pgsql-admin@postgresql.org
Subject: Re: Suppress 'duplicate key' at errorlog?
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: 
 <1162433235.755302.1427760768118.JavaMail.zimbra@zimbra.int.journyx.com>
From: Scott Whitney <scott@journyx.com>
Date: Mon, 30 Mar 2015 19:12:48 -0500 (CDT)
Thread-Topic: Suppress 'duplicate key' at errorlog?
Thread-Index: 8ZWlwCuyL7WiLt1b0ganVJAGZFTYdA==
X-Pg-Spam-Score: -0.8 (/)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

<p dir=3D=22ltr=22>Am I the only one concerned about a product trying to =
duplicate a pkey=3F This is not usually the LAST step. It's early on in the=
 logical process. You have to find and solve the underlying cause.</p>
<br/><div class=3D=22cm=5Fquote=22 style=3D=22 color: #787878=22>On Mon, =
Mar 30, 2015 at 6:17 PM, Scott Ribe &lt;<a href=3D=22mailto:scott=5Fribe@el=
evated-dev.com=22>scott=5Fribe@elevated-dev.com</a>&gt; =
wrote:</div><br><div id=3D=22oldcontent=22 style=3D=22background-color: =
rgb(255, 255, 255); background-position: initial initial; =
background-repeat: initial initial;=22><blockquote style=3D=22=22><p =
dir=3D=22ltr=22>On Mar 30, 2015, at 3:03 PM, Rossi, Maria &lt;maria.=
rossi@us.pgds.com&gt; wrote:
<br>
&gt;=20
<br>
&gt; Hi,
<br>
&gt;&nbsp;=20
<br>
&gt; Is there a way to suppress a =E2=80=98duplicate key=E2=80=99 msg&nbsp;=
 from the errorlog=3F&nbsp; Due to a bug in a 3rd party application,&nbsp; =
this keeps on appearing and I am concerned that it will fill up the =
filesystem.&nbsp;&nbsp;&nbsp; I can delete&nbsp; the old errorlog,&nbsp; =
but if there is any other meaningful msgs out there, I would lose that too.=

<br>

<br>
No way to turn off that specific error message, but you could filter them =
out of the log, being careful of course not to filter any messages which =
might be more meaningful. You could also prevent the errors from being =
raised by using a trigger, but I don't like that idea very much at all.
<br>

<br>

<br>
--=20
<br>
Scott Ribe
<br>
scott=5Fribe@elevated-dev.com
<br>
http://www.elevated-dev.com/
<br>
https://www.linkedin.com/in/scottribe/
<br>
(303) 722-0567 voice
<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>
--=20
<br>
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
<br>
To make changes to your subscription:
<br>
http://www.postgresql.org/mailpref/pgsql-admin
<br>
</p>
</blockquote></div>