> Now you tell us?
>
> If that's the case, I wonder whether probes.o is getting built
> correctly and included in the link. The relevant bits are in
> src/backend/Makefile ... they don't look that easy to mess up,
> but maybe.
I thought I mentioned it in my original message but it wasn't super cl
>I'd read
>
>
https://www.postgresql.org/docs/current/dynamic-trace.html#DEFINING-TRACE-POINTS
>
>
>and then go see if those tracepoints are fully conforming to the
>coding rules in the modified version. A plausible bet is that
>their entries in probes.d don't entirely match up with the calls
>in
> Was the customization done under version control?
Yes it was. My thinking though is that I am getting this error with every
probe, not just the ones in xact.c so I suspect there is something more
than just a code change to the file. I compared the common makefiles and
don't see any changes that w
from stock. postgresql_transaction__commit_semaphore does exist in the
symbol table of both .o files though when compared with objdump.
On Sun, Oct 20, 2024 at 1:50 PM Adrian Klaver
wrote:
> On 10/20/24 09:30, Barry Walker wrote:
> > Hey folks,
>
> > I have compiled vanilla pg16.4
Hey folks,
I'm working on a custom version of Postgres that is roughly in line with
16.4 but has customizations in it. I'm trying to compile this custom
version (on Linux) with `--enable-dtrace` but I'm running into an issue
during the linker stage. I've done a clean and full rebuild but that
does
