|
Lately my database crashed and I’ve
had some strangeness following. I found that some tables would have two
distinct rows with identical primary key. Now, VACUUM complains thusly WARNING: index
"pg_statistic_relid_att_index" contains 2984 row versions, but table
contains 2983 row versions HINT: Rebuild the index with REINDEX. After trying to reindex, I get ERROR: could not create unique index DETAIL: Table contains duplicated
values. I think I’m seeing the same issue –
a duplicated row. I know this should not happen – but does
it in fact come to happen sometimes? Is there a smarter way of dealing with it
than deleting the duplicate? How can these duplicates get produced? And, for pg_statistic in particular, is it
safe to muck with it? What should I do? Thanks Jaime |
*********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. Bear Stearns does not provide tax, legal or accounting advice. You should consult your own tax, legal and accounting advisors before engaging in any transaction. In order for Bear Stearns to comply with Internal Revenue Service Circular 230 (if applicable), you are notified that any discussion of U.S. federal tax issues contained or referred to herein is not intended or written to be used, and cannot be used, for the purpose of: (A) avoiding penalties that may be imposed under the Internal Revenue Code; nor (B) promoting, marketing or recommending to another party any transaction or matter addressed herein. ***********************************************************************
