| 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 16:03:11 |
| Message-ID: | 61090467-0a38-d58b-dfcc-81463e66708c@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)bowt(dot)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 | Content-Type | Size |
|---|---|---|
| dump_block.page | application/octet-stream | 8.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-04-22 18:05:36 | Re: amcheck assert failure |
| Previous Message | Jonathan S. Katz | 2019-04-22 14:20:12 | Re: Possible to store invalid SCRAM-SHA-256 Passwords |