Re: right sibling is not next child

Also, when I tried to run a database-wide VACUUM ANALYZE VERBOSE it
actually doesn't even get to Panel and errors out with:

INFO:  analyzing "public.MaintCode"
INFO:  "MaintCode": scanned 1 of 1 pages, containing 19 live rows and 0
dead rows; 19 rows in sample, 19 estimated total rows
ERROR:  duplicate key violates unique constraint
"pg_statistic_relid_att_index"

MaintCode is a tiny, static table.  Does that indicate further
corruption or is there a more benign explanation?  Could these errors
not be Postgres' fault? (e.g. hardware-related)

Pete