Re: cache lookup failed for index
| От | Nathan Robertson |
|---|---|
| Тема | Re: cache lookup failed for index |
| Дата | |
| Msg-id | AANLkTikVuefbecakovUG6BGz-pJVFJ04us4YKH8VDQA5@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: cache lookup failed for index (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: cache lookup failed for index
|
| Список | pgsql-admin |
This probably connected to the postgres database, not webapp which is
where your problem is.
OK, is there anyway I can force a connection to this database so I can get a look at the tables (webapp)? To be honest, if there is corrupt data in there, that is fine. I'll manually pull it out. I just need to be able to figure out what uncorrupted data is in there so I can determine if it's even worth saving.
where your problem is.
OK, is there anyway I can force a connection to this database so I can get a look at the tables (webapp)? To be honest, if there is corrupt data in there, that is fine. I'll manually pull it out. I just need to be able to figure out what uncorrupted data is in there so I can determine if it's even worth saving.
On Wed, Jun 30, 2010 at 1:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Nathan Robertson <nathan.robertson@gmail.com> writes:This probably connected to the postgres database, not webapp which is
> OK, I ran:
> postgres -O -P -D /cluster/location
where your problem is.The standalone mode isn't very verbose. If you got a prompt back
> backend> reindex table pg_class;
> And then nothing returns. Nothing stating whether it was successful or a
> failure.
without any error then it's OK. Just type ^D at the prompt to exit.
regards, tom lane
В списке pgsql-admin по дате отправления: