On 29 September 2011 23:15, Tom Lane <t...@sss.pgh.pa.us> wrote: > Peter Geoghegan <pe...@2ndquadrant.com> writes: >> I've built Postgres from master, and found that the following fairly >> simple query breaks: > >> select count(*) >> from >> ( >> select >> schemaname >> from pg_stat_user_tables >> order by 1 >> ) sub >> group by schemaname > >> This produces the internal error message "no relation entry for relid >> 1". Why is that? > > Looks like I broke it here: > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=1cb108efb0e60d87e4adec38e7636b6e8efbeb57
Hmm. Although it was obvious to me that this was an internal error, I have to wonder what a novice would have made of it. Specifically, I wonder if there should be an INTERNAL_ERROR severity level, to explicitly advertise that you're not supposed to see this, and to help log analysis tools (including grep) bring these sorts of things to the DBA's attention, as they are surely much more severe than most errors seen in practice. -- 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
