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

Re: Postgres code quality

From: asya999 <asya999(at)gmail(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Postgres code quality
Date: 2012-02-26 02:29:20
Message-ID: (view raw or whole thread)
Lists: pgsql-advocacy
Alvaro Herrera wrote:
>  As far as I know we still haven't configured the coverity tools
> so that they don't report spurious errors in certain safe coding idioms 
> we use, so our true defect density is likely to be lower than the article
> reports.

Actually, you'll be happy to hear that before this year's report and as part
of moving PostgreSQL to the latest version of analysis, we tuned analysis 

Among other things, the analysis now understands the various elog/
ereport(ERROR/PANIC) idioms which got rid of a lot of false positives, 
and we also excluded generated code from analysis results. 

I would expect the results to be quite relevant at this point - if there is
additional tuning to be done, please let us know at 

Asya Kamsky
Coverity, Inc.

View this message in context:
Sent from the PostgreSQL - advocacy mailing list archive at

In response to

pgsql-advocacy by date

Next:From: Chris TraversDate: 2012-02-27 14:03:33
Subject: Re: Postgresql in market
Previous:From: Adrian KlaverDate: 2012-02-25 03:32:44
Subject: Re: Postgres code quality

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