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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
