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

From: Tech 2010 <tch072(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
Date: 2009-11-19 10:42:34
Message-ID: 1216130f-141d-44b0-aace-4980a4c46f5a@a32g2000yqm.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Henk van Lingen 2009-11-19 11:04:47 text search query planning
Previous Message Nicola Farina 2009-11-19 09:55:57 Dblink to Oracle