Re: Making the regression tests halt to attach a debugger

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making the regression tests halt to attach a debugger
Date: 2015-05-18 17:15:53
Message-ID: 555A1E49.8040402@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 05/18/2015 01:05 PM, Tom Lane wrote:
> Meh. You could also add "select pg_backend_pid()" or some such.
> But really, the way I generally do this is to run gdb via a script
> that auto-attaches to the right postgres process if at all possible.
> Removes the whole problem.
>

This should go on the wiki.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-05-18 17:18:26 Re: jsonb concatenate operator's semantics seem questionable
Previous Message Alvaro Herrera 2015-05-18 17:13:51 Re: ERROR: cannot GetMultiXactIdMembers() during recovery