From: | decibel <decibel(at)decibel(dot)org> |
---|---|
To: | Vanessa Lopez <v(dot)lopez(at)open(dot)ac(dot)uk> |
Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: REINDEX "is not a btree" |
Date: | 2009-07-10 17:37:02 |
Message-ID: | 0D21B360-962A-4BE1-A0EF-405E9AA69C74@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jul 10, 2009, at 6:47 AM, Vanessa Lopez wrote:
> I discovered the table that was causing the error, delete it and
> create it again (I miss some data but at least everything else is
> working now)
>
> Yes, for the backup we copy everything we had under /data (the
> directory containing "base", "global", and so on ... we do backups
> every day from the server), and then we restore the whole /data
> directory at once ... but it did not solve the problem ..
Given the problems you've had, I strongly suggest you take a pg_dump
of the database, restore that dump, and use the restored copy. I bet
there's probably other problems lurking in your database.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-07-10 17:37:27 | Re: Overhead of union versus union all |
Previous Message | Jeff Davis | 2009-07-10 17:17:08 | Re: SELECT DISTINCT very slow |