From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Using the rr debugging tool to debug Postgres |
Date: | 2020-04-07 10:36:22 |
Message-ID: | 20200407123622.53d04168@firost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 6 Apr 2020 10:38:31 -0700
Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> rr is a tool that makes gdb much more useful by supporting recording
> and replaying of the program being debugged. I highly recommend trying
> rr if you're somebody that regularly uses gdb to debug Postgres. rr
> implements a gdbserver under the hood, so it's very easy to start
> using once you're already familiar with gdb.
>
> I have written a Wiki page on how to use rr to record and replay
> Postgres executions:
>
> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Recording_Postgres_using_rr_Record_and_Replay_Framework
Thank you Peter!
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2020-04-07 10:40:33 | Re: [Proposal] Global temporary tables |
Previous Message | Amit Kapila | 2020-04-07 10:32:36 | Re: [HACKERS] make async slave to wait for lsn to be replayed |