Re: amcheck assert failure

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: amcheck assert failure
Дата
Msg-id 23979.1555962717@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: amcheck assert failure  (Grigory Smolkin <g.smolkin@postgrespro.ru>)
Ответы Re: amcheck assert failure  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-bugs
Grigory Smolkin <g.smolkin@postgrespro.ru> writes:
> On 04/22/2019 09:05 PM, Peter Geoghegan wrote:
>> The ascii string "blablahblah" has been overwritten at byte offset
>> 1040 (from the beginning of the page). I would take a closer look at
>> what those tests do. Either the problem is in the tests, or your
>> database is haunted, which is outside my area of expertise.

> It`s data corruption test, but I`ve forgot to turn checksums on.
> I`m sorry for wasting your time.

Nonetheless ... do we really want an assertion failure rather than
some more-mundane error report?  Seems like the point of amcheck
is to detect data corruption, so I'd rather get an ERROR than an
assertion (which would not fire in production builds anyway).

            regards, tom lane



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: amcheck assert failure
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: amcheck assert failure