Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
От | Tom Lane |
---|---|
Тема | Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673 |
Дата | |
Msg-id | 18761.1231440033@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673 (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: PANIC: failed to re-find parent key in "100924" for
split pages 1606/1673
|
Список | pgsql-bugs |
Simon Riggs <simon@2ndQuadrant.com> writes: > On Mon, 2009-01-05 at 14:25 -0500, Tom Lane wrote: >> Hmm ... I wonder if this is telling us that our patch here was >> incomplete? >> http://archives.postgresql.org/pgsql-committers/2006-11/msg00004.php >> >> At the time we thought this failure could only occur during _bt_pagedel >> but you have evidently got a case where a split is failing. It might >> just be garden-variety index corruption, or it might be a real bug. > Did you catch this had occurred during recovery? Yes, I did. Which is one of the reasons I think there might be a real bug there, but without any evidence to look at it's hard to do much about it now. (Also, our solution to the underlying problem is quite different now than it was in 8.1, so I'm doubtful that the bug still exists in current code even if it's real in 8.1.) > Can we downgrade the error from PANIC to LOG please? No, that seems utterly unsafe to me. We'd have a corrupt index and nothing to cause it to get repaired. regards, tom lane
В списке pgsql-bugs по дате отправления: