On Fri, Jul 11, 2014 at 11:26 PM, Ravi Kiran wrote:
> 13)n
In gdb, 'n' or 'next' is used to have the debugger switch to the next
line, if you want to stop automatically to the next breakpoint, use
either 'c' of 'continue'.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgr
Hi,
I am facing some problem with gdb for the past few days.
I want to debug nestloop.c in postgresql , so I followed the below steps.
I followed the steps given in the below for collecting the stack trace.
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_
On Tue, Jul 8, 2014 at 12:40 PM, Ravi Kiran
wrote:
> hi,
>
> I am trying to learn how postgresql implements the join algorithms.
>
> So I am trying to learn about the source code of the executor precisely
> the file nodenestloop.c .
>
> In the executor file I have nodenestloop.o but no binary exe
hi,
I am trying to learn how postgresql implements the join algorithms.
So I am trying to learn about the source code of the executor precisely the
file nodenestloop.c .
In the executor file I have nodenestloop.o but no binary executor file.
I am using helios eclipse to edit the source code.
I