Re: Coverity Open Source Defect Scan of PostgreSQL - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Coverity Open Source Defect Scan of PostgreSQL
Date
Msg-id 200603081401.55463.josh@agliodbs.com
Whole thread Raw
In response to Re: Coverity Open Source Defect Scan of PostgreSQL  (Ben Chelf <ben@coverity.com>)
Responses Re: Coverity Open Source Defect Scan of PostgreSQL
List pgsql-hackers
Folks,
> As for Coverity, if the elevel that's passed to the ereport is really a
> constant, the above #ifdef should absolutely do the trick for us so we
> know to stop analyzing on that path...Let me know if it doesn't actually
> do that ;)

Um, I think the answer is to train Coverity, not change our code to avoid 
the false-positives.  I know that Coverity is sophisticated enough to, for 
example, be programed to understand that elog(ERROR) does not continue.  

Actually, I thougth that Neil/eDB did this with their copy.  Is there any 
way to get a copy of that "training configuration"?

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: Merge algorithms for large numbers of "tapes"
Next
From: "Jonah H. Harris"
Date:
Subject: Re: Coverity Open Source Defect Scan of PostgreSQL