On Mon, Feb 20, 2017 at 02:54:22PM -0800, Peter Geoghegan wrote: > On Mon, Feb 20, 2017 at 2:38 PM, Bruce Momjian <br...@momjian.us> wrote: > > I can't think of any cases where we warn of possible corruption only in > > the server logs. > > It's just like any case where there was a bug in Postgres that could > have subtly broken index builds. We don't make the next point release > force users to REINDEX every possibly-affected index every time that > happens. Presumably this is because they aren't particularly likely to > be affected by any given bug, and because it's pretty infeasible for > us to do so anyway. There aren't always easy ways to detect the > problem, and users will never learn to deal with issues like this well > when it is by definition something that should never happen.
Well, the release notes are a clear-enough communication for a need to reindex. I don't see a LOG message as similar. Don't we have other cases where we have to warn administrators? We can mark the indexes as invalid but how would we report that? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers