On 05/14/2010 08:49 PM, Igor Neyman wrote: > > >> -----Original Message----- >> From: Catalin BOIE [mailto:cboie-pgsql@xxxxxx] >> Sent: Friday, May 14, 2010 5:43 AM >> To: pgsql-general@xxxxxxxxxxxxxx >> Subject: Re: PANIC: corrupted item pointer: 32766 >> >> Some more info. >> >> The PANIC happens several times per minute, so, is really bad for me. >> >> I tried to narrow down based on a field (timestamp) and I >> found some bad "points", but I cannot delete them (same PANIC >> message appear). >> >> Do you have any idea how can I correct that entries? >> >> The worry part is how this happened?! >> >> Thank you! >> >> RAM is 16GiB, 16 "cpus" (including hyperthreading). >> >> On 05/14/2010 09:32 AM, Catalin BOIE wrote: >>> Hello! >>> >>> I have a serious problem with one of my tables. >>> >>> Version: postgresql-server-8.4.3-1.fc12.x86_64 >>> Kernel: kernel-2.6.32.11-99.fc12.x86_64 >>> >>> I reindexed all indexes on that table, but I still cannot >> workaround >>> this problem. >>> >>> Memory is ECC and the storage is RAID10 (BIOS reported it OK). >>> >>> How I can fix this problem? >>> >>> Thank you! >>> >> >> >> -- >> Catalin BOIE >> > > If you can read other (good) records from this table, then: > > 1. create "intermediate table > 2. copy all "good" records from original table into the new table > 3. drop original table > 4. rename "intermediate" table to "original" name > 5. re-created required indexes (and any other objects dependent on this > table) > > > Igor Neyman > Only now I seen your message, but this is exactly what I did. I built a script that did this: for (uid = 1; uid < 'SELECT MAX(uid) FROM table'; uid++) INSERT INTO new_table SELECT * FROM table WHERE uid = $uid uid is the primary key and is a sequence. I managed to recover all rows (around 5 millions), except 22, that where inserted at the same time. Seems that not the rows where bad, but the link to a page where they were stored. I am not familiar with the PostgreSQL code. I am also not familiar with the structure on mem/disk of the database. So, have mercy with my explanations. I am very sure that rows were inserted one after another. Having no more ideas, I dropped all the indexes to the bad table. No change. ANALYZE worked. VACUUM generated the same error message. fsync was at the default value (I assume is on). For now I fixed the problem, but I am worried that the problem will come back, because I have no idea what could generate this corruption. Maybe, would be nice that this message to dump more data to help somebody to debug the problem. I searched this error and I seen that there are only around 5 cases. So, is seldom, but is a bad one. Thanks to everybody for their support! P.S. I still have the bad table. If you want me to debug something, just ask. -- Catalin BOIE -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
