Matthias.Pitzl@xxxxxx 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
