Re: amcheck assert failure - Mailing list pgsql-bugs

From Grigory Smolkin
Subject Re: amcheck assert failure
Date
Msg-id d0473f0e-46bc-839f-1992-ff3564bf16ea@postgrespro.ru
Whole thread Raw
In response to Re: amcheck assert failure  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: amcheck assert failure  (Peter Geoghegan <pg@bowt.ie>)
Re: amcheck assert failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 04/22/2019 09:05 PM, Peter Geoghegan wrote:
> On Mon, Apr 22, 2019 at 9:03 AM Grigory Smolkin
> <g.smolkin@postgrespro.ru> wrote:
>> Wow, that` neat, thank you for a dump instruction!
>> Attached.
> This looks like it was deliberately corrupted. Line pointer 255 is an
> LP_REDIRECT, line pointer, while line pointer 256 and 257 are
> LP_UNUSED, which should never happen.
>
> 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.
>
I`m so stupid >.<
It`s data corruption test, but I`ve forgot to turn checksums on.
I`m sorry for wasting your time.

-- 
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company




pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: amcheck assert failure
Next
From: Tom Lane
Date:
Subject: Re: xpath insert unexpected newlines