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 e11a49cb-570a-60b7-707d-7084c8de0e61@2ndquadrant.com
Whole thread Raw
In response to Re: remove ancient pre-dlopen dynloader code  (Andres Freund <andres@anarazel.de>)
Responses Re: remove ancient pre-dlopen dynloader code
Re: remove ancient pre-dlopen dynloader code
Re: remove ancient pre-dlopen dynloader code
List pgsql-hackers
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.

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

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Proposal to add work_mem option to postgres_fdw module
Next
From: Rafia Sabih
Date:
Subject: Re: Hint to set owner for tablespace directory