Re: gdb with postgres - Mailing list pgsql-hackers

From HuangQi
Subject Re: gdb with postgres
Date
Msg-id BANLkTimXJSUX9sAS=J9app3OcVMaarBmEg@mail.gmail.com
Whole thread Raw
In response to Re: gdb with postgres  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
<div class="gmail_quote">On 6 June 2011 21:57, Kevin Grittner <span dir="ltr"><<a
href="mailto:Kevin.Grittner@wicourts.gov">Kevin.Grittner@wicourts.gov</a>></span>wrote:<br /><blockquote
class="gmail_quote"style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left:
1ex;"><divclass="im">HuangQi <<a href="mailto:huangqiyx@gmail.com">huangqiyx@gmail.com</a>> wrote:<br /><br
/></div><divclass="im">>>> (gdb) b qp_add_paths_to_joinrel<br /> >>> Breakpoint 1 at 0x1a6744: file
joinpath.c,line 67.<br /> >>> (gdb) attach 23903<br /><br /></div><div class="im">> If I enter c, gdb will
directlyfinish executing this process and<br /> > current query will finish.<br /><br /></div>Are you absolutely
surethat running your query will result in a<br /> call to this function?<br /><font color="#888888"><br /> -Kevin<br
/></font></blockquote></div><br/><br />Thanks guys for your idea. I found the solution. Because after made some change
inpostgres and make them, I didn't stop the server first. Now I stop it and start after reinstall, then using gdb is
justfine. Thanks for your ideas.<br clear="all" /><br />-- <br />Best Regards<br />Huang Qi Victor<br /> 

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: contrib/citext versus collations
Next
From: Dave Page
Date:
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch