dbTalk Databases Forums  

error during vacuum

comp.databases.postgresql.novice comp.databases.postgresql.novice


Discuss error during vacuum in the comp.databases.postgresql.novice forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Michael Guerin
 
Posts: n/a

Default error during vacuum - 05-25-2004 , 08:35 PM






INFO: analyzing "pg_catalog.pg_type"
INFO: "pg_type": 5731 pages, 265 rows sampled, 265 estimated total rows
INFO: vacuuming "pg_catalog.pg_attribute"
ERROR: failed to re-find parent key in "pg_attribute_relid_attnam_index"

I get this error when I run Vacuum verbose analyze, any ideas? I
recently re-created a number of tables and indexes b/c we needed to
change to bigints.


Thanks
Michael

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match


Reply With Quote
  #2  
Old   
Tom Lane
 
Posts: n/a

Default Re: error during vacuum - 05-25-2004 , 11:10 PM






Michael Guerin <guerin (AT) rentec (DOT) com> writes:
Quote:
ERROR: failed to re-find parent key in "pg_attribute_relid_attnam_index"
Oh? What PG version is this exactly?

Your best bet is probably to REINDEX pg_attribute, but it would be wise
to try to understand what happened before you wipe out the evidence...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match



Reply With Quote
  #3  
Old   
Michael Guerin
 
Posts: n/a

Default Re: error during vacuum - 05-25-2004 , 11:36 PM



Tom Lane wrote:

Quote:
Michael Guerin <guerin (AT) rentec (DOT) com> writes:


ERROR: failed to re-find parent key in "pg_attribute_relid_attnam_index"



Oh? What PG version is this exactly?

Your best bet is probably to REINDEX pg_attribute, but it would be wise
to try to understand what happened before you wipe out the evidence...

regards, tom lane


7.4.1 , where should I look for some hints on what went wrong? I'll
search the logs for anything meaningful, should I look elsewhere?

thanks
michael


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.