Re: remove ancient pre-dlopen dynloader code - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: remove ancient pre-dlopen dynloader code
Date
Msg-id 92fe6039-16ea-483a-2cf9-ea58955006ab@2ndquadrant.com
Whole thread Raw
In response to Re: remove ancient pre-dlopen dynloader code  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: remove ancient pre-dlopen dynloader code
List pgsql-hackers
On 31/08/2018 10:52, Peter Eisentraut wrote:
> On 16/08/2018 16:10, Andres Freund wrote:
>>>> If I had my druthers, we'd just remove all that configure magic for
>>>> selecting these files and just use ifdefs.  Personally I find it
>>>> occasionally that they're linked into place, rather than built under
>>>> their original name.
>>>
>>> Even if we all agreed that was an improvement (which I'm not sure of),
>>> it wouldn't fix this problem would it?  On affected platforms, the
>>> file would still be empty after preprocessing.
>>
>> Well, that depends on what you put into that file, it seems
>> realistically combinable with a bunch of non-conditional code...
> 
> How about this: We only have two nonstandard dlopen() implementations
> left: Windows and (old) HP-UX.  We move those into src/port/dlopen.c and
> treat it like a regular libpgport member.  That gets rid of all those
> duplicative empty per-platform files.

Updated patch.  It needed some adjustments for Windows, per Appveyor,

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: "Shinoda, Noriyoshi (PN Japan GCS Delivery)"
Date:
Subject: RE: [HACKERS] Proposal to add work_mem option to postgres_fdw module
Next
From: Dilip Kumar
Date:
Subject: Re: pg_verify_checksums failure with hash indexes