Re: amcheck assert failure

From: Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: amcheck assert failure
Date: 2019-04-22 19:48:23
Message-ID: d0473f0e-46bc-839f-1992-ff3564bf16ea@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 04/22/2019 09:05 PM, Peter Geoghegan wrote:
> On Mon, Apr 22, 2019 at 9:03 AM Grigory Smolkin
> <g(dot)smolkin(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-04-22 19:48:38 Re: xpath insert unexpected newlines
Previous Message Peter Geoghegan 2019-04-22 18:05:36 Re: amcheck assert failure