From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Matthias(dot)Pitzl(at)izb(dot)de |
Cc: | scotty(at)linuxtime(dot)it, pgsql-general(at)postgresql(dot)org |
Subject: | Re: can't start postgresql |
Date: | 2006-11-14 15:34:20 |
Message-ID: | 20061114153420.GA30115@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Matthias(dot)Pitzl(at)izb(dot)de wrote:
> He's just trying to do what you told him.
> But the use of initdb won't correct the problem Igor got. There's something
> wrong with his database so that he can't start the postmaster process:
> > PANIC: failed to re-find parent key in "23724"
>
> Unfortunately i don't have any idea how to solve this issue :(
I'd think starting a standalone backend and issuing a "reindex database"
should be enough to get him started. Now, the problem is figuring _how_
the index got in that state; or even _what_ index is the problematic
one. (I think it would be possible to find out by setting the
"log_error_verbosity" parameter to "verbose").
If it's a hardware problem, one would think it deserves some diagnosis.
It could be the btree bug Tom fixed last week, but I'm not sure if this
is really a consequence of it.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-11-14 15:36:40 | Re: can't start postgresql |
Previous Message | Matthias.Pitzl | 2006-11-14 15:22:42 | Re: can't start postgresql |