Skip site navigation (1) Skip section navigation (2)

Re: Performance problems testing with Spamassassin 3.1.0

From: John Arbash Meinel <john(at)arbash-meinel(dot)com>
To: josh(at)agliodbs(dot)com
Cc: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>,Matthew Schumacher <matt(dot)s(at)aptalaska(dot)net>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance problems testing with Spamassassin 3.1.0
Date: 2005-07-29 18:29:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Josh Berkus wrote:

>>      EXCEPTION WHEN unique_violation THEN
>I seem to remember that catching an exception in a PL/pgSQL procedure was a 
>large performance cost.   It'd be better to do UPDATE ... IF NOT FOUND.
Actually, he was doing an implicit UPDATE IF NOT FOUND in that he was doing:


IF found THEN return;


So really, the exception should never be triggered.

In response to

pgsql-performance by date

Next:From: Jeffrey W. BakerDate: 2005-07-29 18:55:42
Subject: Re: Performance problems on 4/8way Opteron (dualcore) HP
Previous:From: Luke LonerganDate: 2005-07-29 17:54:08
Subject: Re: [PATCHES] COPY FROM performance improvements

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group