Re: Help Resolving Compiler Errors With enable-dtrace Flag

From: Barry Walker <mstrchef7(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
Date: 2024-10-20 21:29:41
Message-ID: CAAiHg9Wjx_yMHseUPy8NGFVVXAepF0jTF4Oec6v_E7ZTzZ1kog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>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 the source code. You could compare the relevant bits of code
>between vanilla and modified 16.4 if the problem isn't immediately
>obvious.
>
> regards, tom lane

I've taken a look at the probes.d file and there are no changes between the
modified and vanilla versions of the file, and the probes are called with
the same args. This is happening for every probe in the probes.d file.
Since I'm getting those errors it looks like the generated probes.h file is
also properly being used. Do you know where the
postgresql_transaction__commit_semaphore
symbol should be defined?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-10-20 21:52:53 Re: Help Resolving Compiler Errors With enable-dtrace Flag
Previous Message Adrian Klaver 2024-10-20 21:12:28 Re: Basebackup fails without useful error message