| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, "noloader(at)gmail(dot)com" <noloader(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clang 3.3 Analyzer Results |
| Date: | 2013-11-12 02:13:48 |
| Message-ID: | 20896.1384222428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> It does seem hard to believe that clang tools would find as enough
> problems that were missed by Coverity and Valgrind to account for
> all the warnings that are scrolling by; but it looks like it has
> pointed out at least *one* problem that's worth fixing.
Yeah, that's the thing --- quite a lot of people have looked at
Postgres with Coverity already. If Clang is throwing up lots and
lots of warnings, the odds are *very* high that most of them are
false positives. Running through such a list to see if there's
anything real isn't all that exciting a prospect.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2013-11-12 02:18:32 | Question about forced immediate checkpoints during create database |
| Previous Message | Tom Lane | 2013-11-12 01:51:53 | Re: Postgres 9.3.1 and Self Test Failure "pg_regress: no *.source files found" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-12 02:19:54 | Re: MVCC snapshot timing |
| Previous Message | Tom Lane | 2013-11-12 01:59:35 | Re: MVCC snapshot timing |