Re: pgsql: Refactor dlopen() support - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: Refactor dlopen() support
Date
Msg-id 3574.1536329946@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Refactor dlopen() support  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: pgsql: Refactor dlopen() support  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 07/09/2018 08:30, Tom Lane wrote:
>> Buildfarm member locust doesn't like this much.  I've been able to
>> reproduce the problem on an old Mac laptop running the same macOS release,
>> viz 10.5.8.  (Note that we're not seeing it on earlier or later releases,
>> which is odd in itself.)

> Nothing should have changed on macOS except that the intermediate
> functions pg_dl*() were replaced by direct calls to dl*().  Very strange.

Somehow or other, the changes you made in dfmgr.c's #include lines
have made it so that find_rendezvous_variable's local "bool found"
variable is actually of type _Bool (which is word-wide on these
machines).  However, hash_search thinks its output variable is
of type pointer to "typedef char bool".  The proximate cause of
the observed failure is that find_rendezvous_variable sees "found"
as true when it should not, and thus fails to zero out the variable's
value.

No time to look further right now, but there's something rotten
about the way we're handling bool.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Removing useless \. at the end of copy in pgbench
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: schema variables