Re: Bug in bttext_abbrev_convert() - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Bug in bttext_abbrev_convert()
Date
Msg-id CAM3SWZQWG7X6K=EEwqbzMueuG5LiaQdKAonYL5BoOWFTEWH=3A@mail.gmail.com
Whole thread Raw
In response to Re: Bug in bttext_abbrev_convert()  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Bug in bttext_abbrev_convert()
List pgsql-hackers
On Tue, Jun 30, 2015 at 5:25 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> Isn't this the kind of thing Coverty's supposed to find?

I don't know, but in general I'm not very excited about static
analysis tools. The best things that they have going for them is that
they're available, and don't require test coverage in the same way as
running the regression tests with Valgrind enabled.

There is no real testing of sorting in the regression tests. It would
be nice to have a way of generating a large and varied selection of
sort operations programmatically, to catch this kind of thing.
pg_regress is not really up to it. The same applies to various other
cases where having a lot of "expected" output makes using pg_regress
infeasible.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Bug in bttext_abbrev_convert()
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup and replication slots