Re: amcheck assert failure

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: amcheck assert failure
Date: 2019-04-20 21:37:35
Message-ID: CAH2-Wz=r2g0pet4hVPi88Yh+uqRmMphEON0U9Yd28HSW+ac7vQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Apr 20, 2019 at 2:00 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Obviously you'll need to figure out which block number the problem
> page is located in before you do this, but that shouldn't be hard --
> get a coredump and inspect the state from amcheck a few frames down.

Alternatively, you could dump the page image from within gdb. Go to
the frame for _bt_check_natts() (e.g., enter "f 1"), and then dump the
contents of the page to file:

(gdb) dump binary memory /tmp/dump_block.page page (page + 8192)

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2019-04-20 23:06:06 Re: amcheck assert failure
Previous Message Peter Geoghegan 2019-04-20 21:00:37 Re: amcheck assert failure