Dimitris Karampinas <dkarampin@xxxxxxxxx> writes: > Is there any way to get the call stack of a function when profiling > PostgreSQL with perf ? > I configured with --enable-debug, I run a benchmark against the system and > I'm able to identify a bottleneck. > 40% of the time is spent on an spinlock yet I cannot find out the codepath > that gets me there. > Using --call-graph with perf record didn't seem to help. Call graph data usually isn't trustworthy unless you built the program with -fno-omit-frame-pointer ... regards, tom lane
