Re: amcheck assert failure - Mailing list pgsql-bugs

From Grigory Smolkin
Subject Re: amcheck assert failure
Date
Msg-id 61090467-0a38-d58b-dfcc-81463e66708c@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>)
List pgsql-bugs
I`m sorry for a delay, was away from PC during weekend.

On 04/21/2019 02:06 AM, Peter Geoghegan wrote:
> On Sat, Apr 20, 2019 at 2:37 PM Peter Geoghegan <pg@bowt.ie> wrote:
>> 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:
> I was inspired to do a write-up on this for the Wiki:
>
>
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Dumping_a_page_image_from_within_GDB
>
> Seems like a good idea to centralize knowledge of backend
> instrumentation that's useful for bug reports, even beyond GDB.
>

Wow, that` neat, thank you for a dump instruction!
Attached.

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


Attachment

pgsql-bugs by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: Possible to store invalid SCRAM-SHA-256 Passwords
Next
From: Peter Geoghegan
Date:
Subject: Re: amcheck assert failure