Skip site navigation (1) Skip section navigation (2)

Re: right sibling is not next child

From: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: right sibling is not next child
Date: 2006-04-11 23:42:54
Message-ID: 443BF8AE020000BE00002C5A@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
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



In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-04-12 03:00:44
Subject: Re: right sibling is not next child
Previous:From: Peter BrantDate: 2006-04-11 23:38:20
Subject: Re: right sibling is not next child

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group