On 29 January 2012 20:39, Josh Berkus <j...@agliodbs.com> wrote: > >> This is the kind of thing that could go unnoticed for a long time, >> simply because it is not highlighted any more prominently than a >> routine error message like an integrity constraint violation. I >> continue to maintain that we should have a new severity level for this >> sort of thing. > > Huh? I don't follow you at all Peter.
I mean that we should change code like this: elog(ERROR, "could not find plan for CTE \"%s\"", rte->ctename) to this: elog(INTERNAL_ERROR, "could not find plan for CTE \"%s\"", rte->ctename) (which would necessitate creating a new severity level, INTERNAL_ERROR). So that DBAs could find these kinds of problems systematically. This is an error message that we expect no one to see. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
