Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43714=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1YciZj-00012I-VI
 for pgsql-admin@arkaria.postgresql.org; Mon, 30 Mar 2015 22:54:32 +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+M43714=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1YciZj-00035R-Al
 for pgsql-admin@arkaria.postgresql.org; Mon, 30 Mar 2015 22:54:31 +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 1YciZi-00035F-GW
 for pgsql-admin@postgresql.org; Mon, 30 Mar 2015 22:54:30 +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 1YciZe-00070b-ET
 for pgsql-admin@postgresql.org; Mon, 30 Mar 2015 22:54:29 +0000
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id 309013000BF;
 Mon, 30 Mar 2015 17:54:22 -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 L9njhi_0EEfP; Mon, 30 Mar 2015 17:54:22 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id E4FDC301F55;
 Mon, 30 Mar 2015 17:54:21 -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 rWgayKBM4njP; Mon, 30 Mar 2015 17:54:21 -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 9D3B03000BF;
 Mon, 30 Mar 2015 17:54:21 -0500 (CDT)
MIME-Version: 1.0
X-Mailer: CloudMagic
X-Mailer: Zimbra 8.6.0_GA_1153 (MobileSync - CloudMagic)
X-Cm-Message-Id: 
 1427756060257264a61ef9b629534f7e83d4498bea88e4f05519d41c3eda1674966449
In-Reply-To: 
 <CAKFQuwaQVcyePbseX56S3joRspLYAnmiVuDqbcdQ1zSRJHD19Q@mail.gmail.com>
References: <33A4D5087BF0D44DA69C5EEF666BC1D74263DD2C@usprmbp01c>
To: "David G. Johnston" <david.g.johnston@gmail.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: 
 <1114474783.754620.1427756060642.JavaMail.zimbra@zimbra.int.journyx.com>
From: Scott Whitney <scott@journyx.com>
Date: Mon, 30 Mar 2015 17:54:21 -0500 (CDT)
Thread-Topic: Suppress 'duplicate key' at errorlog?
Thread-Index: WWZwCMpOG1Gzb3fpd8WUdvnSSqa1ZQ==
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>I =5Fdo=5F want to phone in on the whole duplicate key =
issue.</p>
<p dir=3D=22ltr=22>Sure, this could be a race condition. It could be bad =
programming. It could be a variety of things.</p>
<p dir=3D=22ltr=22>You ABSOLUTELY do not want to ignore that. Ignoring and =
moving on will cause consistency problems. Catch it and add it to a log or =
an email. Continue.</p>
<p dir=3D=22ltr=22>Do NOT silently ignore something trying to add a =
duplicate key.</p>
<br/><div class=3D=22cm=5Fquote=22 style=3D=22 color: #787878=22>On Mon, =
Mar 30, 2015 at 5:45 PM, David G. Johnston &lt;<a href=3D=22mailto:david.g.=
johnston@gmail.com=22>david.g.johnston@gmail.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><div =
dir=3D=22ltr=22><div class=3D=22gmail=5Fdefault=22 style=3D=22font-family:a=
rial,helvetica,sans-serif=22><span style=3D=22font-family:arial,=
sans-serif=22>On Mon, Mar 30, 2015 at 2:03 PM, Rossi, Maria </span><span =
dir=3D=22ltr=22 style=3D=22font-family:arial,sans-serif=22>&lt;<a =
href=3D=22mailto:maria.rossi@us.pgds.com=22>maria.rossi@us.pgds.=
com</a>&gt;</span><span style=3D=22font-family:arial,sans-serif=22> =
wrote:</span><br></div><div class=3D=22gmail=5Fextra=22><div =
class=3D=22gmail=5Fquote=22><blockquote class=3D=22gmail=5Fquote=22 =
style=3D=22margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=22=
>





<div lang=3D=22EN-US=22>
<div>
<p class=3D=22MsoNormal=22>Hi,<u></u><u></u></p>
<p class=3D=22MsoNormal=22><u></u>&nbsp;<u></u></p>
<p class=3D=22MsoNormal=22>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 =
3<sup>rd</sup> 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=
.<u></u><u></u></p>
<p class=3D=22MsoNormal=22><u></u>&nbsp;<u></u></p>
<p class=3D=22MsoNormal=22>Thanks. <span class=3D=22HOEnZb=22><font =
color=3D=22#888888=22><u></u><u></u></font></span></p><span =
class=3D=22HOEnZb=22><font color=3D=22#888888=22>
<p class=3D=22MsoNormal=22><u></u>&nbsp;<u></u></p>
<p class=3D=22MsoNormal=22><b><span style=3D=22font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:teal=22>Maria
</span></b><span style=3D=22color:#1f497d=22><u></u><u></u></span></p>
<p class=3D=22MsoNormal=22><u></u>&nbsp;<u></u></p>
</font></span></div>
</div>

</blockquote></div><br></div><div class=3D=22gmail=5Fextra=22><div =
class=3D=22gmail=5Fdefault=22 style=3D=22font-family:arial,helvetica,=
sans-serif=22>Not in any way that doesn't also entail the =22but if there =
is any other meaningful msgs out there, I would lose that too.=22 risk.=
</div><div class=3D=22gmail=5Fdefault=22 style=3D=22font-family:arial,=
helvetica,sans-serif=22><br></div><div class=3D=22gmail=5Fdefault=22 =
style=3D=22font-family:arial,helvetica,sans-serif=22>Stop thinking about =
the limited problem of removing the excessive messages and just learn how =
to deal with high-volume log situations generally.&nbsp; At worse you could=
 a simple log rotation and archive with a cleanup =22sed=22 script that =
deletes these messages.&nbsp; Suggest setting =22application=5Fname=22 in =
order to be more targeted.</div><div class=3D=22gmail=5Fdefault=22 =
style=3D=22font-family:arial,helvetica,sans-serif=22><br></div><div =
class=3D=22gmail=5Fdefault=22 style=3D=22font-family:arial,helvetica,=
sans-serif=22>David J.=E2=80=8B</div><br></div></div>
</blockquote></div>