| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Using the rr debugging tool to debug Postgres |
| Date: | 2020-04-06 17:38:31 |
| Message-ID: | CAH2-Wzknuuzb0eqoinBeBwPKUAmyVt_VP5cR17HYUvX2=iH7VA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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:
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2020-04-06 17:40:38 | Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch) |
| Previous Message | Magnus Hagander | 2020-04-06 17:32:45 | Re: where should I stick that backup? |