Re: Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227

From: Thom Brown <thombrown(at)gmail(dot)com>
To: Tech 2010 <tch072(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
Date: 2009-11-19 14:22:44
Message-ID: bddc86150911190622y34c0e249rd63caeaad254b4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/11/19 Tech 2010 <tch072(at)gmail(dot)com>:
> On 18 nov., 16:48, Tech 2010 <tch(dot)(dot)(dot)(at)gmail(dot)com> wrote:
>> On 18 nov., 13:40, thombr(dot)(dot)(dot)(at)gmail(dot)com (Thom Brown) wrote:> 2009/11/18 Tech 2010 <tch(dot)(dot)(dot)(at)gmail(dot)com>:
>>
>> > > Hello!
>>
>> > > How do I location of this pointer and how do I zero it so I can access
>> > > the rest of the data?
>>
>> > > "zero_damaged_pages = true" did not help in this case, because I
>> > > always get same numbers being zeroed. This is with 8.4.0 and 8.4.1.
>>
>> > > Thanks.
>>
>> > You probably just need to reindex a table.  Try vacuuming each table
>> > individually until you get this error, or just check the vacuum log
>> > output to identify it, then just run a REINDEX on it.
>>
>> xy=# reindex table xy_data;
>> ERROR:  concurrent insert in progress
>
> Should I drop and recreate indexes?
>

That might be a good idea. Use the CREATE INDEX CONCURRENTLY command
to prevent that previous error message from appearing.

Regards

Thom

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Lavoie 2009-11-19 14:42:36 Re: Dblink to Oracle
Previous Message Peter Eisentraut 2009-11-19 12:58:34 Re: Enum on-disk format