Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
Дата
Msg-id CAH2-Wznps8CcjbmRAmOMqv5K6pKZQxR0TTQLBhQAu+PxynmjBQ@mail.gmail.com
обсуждение исходный текст
Ответ на backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST  (yuansong <yyuansong@126.com>)
Ответы Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
Список pgsql-hackers
On Thu, Nov 21, 2024 at 10:03 AM yuansong <yyuansong@126.com> wrote:
> Should nhtids be less than or equal to IndexTupleSize(oposting)?
>  Why is nhtids larger than IndexTupleSize(oposting) ? I think there should be an error in the master host writing the
wallog. 
> Does anyone know when this will happen?

It'll happen whenever there is a certain kind of data corruption.

There were complaints about issues like this in the past. But those
complaints seem to have gone away when more hardening was added to the
code that runs during original execution (not the REDO routine code,
which can only do what it is told to do by the WAL record).

You're using PostgreSQL 13.2, which is a very old point release that
lacks this hardening -- the current 13 point release is 13.18, so
you're missing a lot. Had you been on a later point release you'd very
probably have still had the issue with corruption (which could be from
bad hardware), but you likely would have avoided the problem with the
REDO routine crashing like this.

--
Peter Geoghegan



В списке pgsql-hackers по дате отправления: