Not sure how harmful they are, but there sure are a lot of them!
Most are because of the way the database was originally migrated from
Oracle to PostgreSQL. There are a couple PostgreSQL changes that need
to be done in sanity.cgi also. Neither of which I have had time to
address lately. I am going to revisit this all soon and clean up the
PostgreSQL port of Bugzilla to be more in line with the latest
Bugzilla CVS if someone else doesnt beat me to it.
This problem is still there...
Yes. Work has not been done yet to clean out the database clutter. I will need
to make a script to use sanitycheck.cgi's output to go in and remove the clutter
at some point in the future. Hopefully with new application level checks and
other db checks further clutter should not occur over time.
Is this still there with 3.2? I do not have permissions to run sanitycheck anymore, so can't check myself.
We have made even more effort with this migration to clear out as much of the clutter as possible and have narrowed down to just a few smaller sections. We will continue to fix up the remaining data issues now that they upgrade has past.
Sanitycheck.cgi is only accessible by admin users now and should not be accessible to the public.
Thanks for the report.