From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Fix bogus size calculation introduced by commit cc5f81366. |
Date: | 2017-09-17 21:58:19 |
Message-ID: | CAEepm=2W_1c1tY65ZWc-sPF1Ma-YruQTov+UmmDDOgRZkhRRDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Mon, Sep 18, 2017 at 3:35 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Fix bogus size calculation introduced by commit cc5f81366.
>
> The elements of RecordCacheArray are TupleDesc, not TupleDesc *.
> Those are actually the same size, so that this error is harmless,
> but it's still wrong --- and it might bite us someday, if TupleDesc
> ever became a struct, say.
>
> Per Coverity.
Thanks.
While googling around trying to find where I could read Coverity's
output myself I was intrigued to see that https://scan.coverity.com
offers integration with Travis CI[1], which suggests the possibility
of automatically scanning all Commitfest submissions. The trouble is
that for projects over 1 million lines of code they limit scans to one
per day, so it'd take over 200 days to get through the current
Commitfest, assuming no one ever posted new versions or committed
anything in the meantime. Hah. I guess Coverity analysis is going to
have to remain post-commit only.
[1] https://scan.coverity.com/travis_ci
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-09-17 22:22:18 | Re: pgsql: Fix transient mdsync() errors of truncated relations due to 72a9 |
Previous Message | Tom Lane | 2017-09-17 21:04:32 | pgsql: Doc: update v10 release notes through today. |