Unfortunately the people remaining are just as lost as me. No one has attempted to build with dtrace so I'm in uncharted territory.
A diff of the object file doesn't give any useful information, the custom version has a lot of differences since there have been a number of changes 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 <adrian.kla...@aklaver.com> wrote: > On 10/20/24 09:30, Barry Walker wrote: > > Hey folks, > > > I have compiled vanilla pg16.4 with the same flags and the probes got > > created and linked as expected with no issues so I'm assuming there is > > some difference in the custom version that is causing the errors but I'm > > having a hard time tracking it down. I'm wondering if anyone here has > > any experience with this error or has any hints as to why the linker > > can't find these definitions or even just where the actual definitions > > for these probes should live so I can try to work backwards and see if > > there is any differences in the custom version that is messing with > > the linker. > > Talking to the folks that created the custom version is not possible? > > If you do a diff on: > > access/transam/xact.o > > between the stock and custom version does it shed any light? > > > > > Thanks! > > -- > Adrian Klaver > adrian.kla...@aklaver.com > >
