Re: Suppress 'duplicate key' at errorlog?

Thanks for all the comments/suggestions.

As I mentioned, this is a 3rd-party software so what I can do to it is none or limited at best.     I will try to
filterthe errorlog.  Another option is to set the log_min_messages and log_min_error_statement to log.
 

Maria 

-----Original Message-----
From: Jerry Sievers [mailto:gsievers19@comcast.net] 
Sent: Monday, March 30, 2015 8:54 PM
To: Scott Whitney
Cc: Scott Ribe; Rossi, Maria; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Suppress 'duplicate key' at errorlog?

Scott Whitney <scott@journyx.com> writes:

> Am I the only one concerned about a product trying to duplicate a 
> pkey? This is not usually the LAST step. It's early on in the logical process. You have to find and solve the
underlyingcause.
 

I've seen lazy developers use a try insert/update if fail to implement a poor man's upsert...  a feature much sought
afterand only now being seriously developed for Postgres.
 

So... whether or not it's a bug is application dependent.

Yes I'd question a 3rd party about this if the product wasn't developed in house and/or fully open to code review to
havethem tell me "we did it that way on purpose" though rather than just declaring it a nuisance.
 

FWIW


> On Mon, Mar 30, 2015 at 6:17 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>
>     On Mar 30, 2015, at 3:03 PM, Rossi, Maria <maria.rossi@us.pgds.com> wrote:
>     >
>     > Hi,
>     > 
>     > Is there a way to suppress a ‘duplicate key’ msg  from the errorlog?  Due to a bug in a 3rd party
application, this keeps on appearing and I am concerned that it
 
>     will fill up the filesystem.    I can delete  the old errorlog,  but if there is any other meaningful msgs out
there,I would lose that too.
 
>    
>     No way to turn off that specific error message, but you could filter them out of the log, being careful of course
notto 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
verymuch at all.
 
>
>     --
>     Scott Ribe
>     scott_ribe@elevated-dev.com
>     http://www.elevated-dev.com/
>     https://www.linkedin.com/in/scottribe/
>     (303) 722-0567 voice
>
>     --
>     Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>     To make changes to your subscription:
>     http://www.postgresql.org/mailpref/pgsql-admin
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800