| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alex Shulgin <ash(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
| Date: | 2014-12-04 15:10:35 |
| Message-ID: | 5480796B.7020203@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 12/04/2014 10:50 PM, Alex Shulgin wrote:
> Is there a way to pause the bootstrap process so I can attach gdb to it?
With a newer gdb, you can instead tell gdb to follow all forks. I wrote
some notes on it recently.
http://blog.2ndquadrant.com/processes-breakpoints-watchpoints-postgresql/
I've found it really handy when debugging crashes in regression tests.
However, it's often simpler to just:
ulimit -c unlimited
make check
(or whatever your crashing test is) then look at the core files that are
produced.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Shulgin | 2014-12-04 15:14:47 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
| Previous Message | Alex Shulgin | 2014-12-04 14:50:24 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Shulgin | 2014-12-04 15:14:47 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |
| Previous Message | Alex Shulgin | 2014-12-04 14:50:24 | Re: [COMMITTERS] pgsql: Keep track of transaction commit timestamps |