Re: Inconsistencies around defining FRONTEND - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Inconsistencies around defining FRONTEND
Date
Msg-id 20220824015544.pxjxnv6dbjg4ytom@awork3.anarazel.de
Whole thread Raw
In response to Re: Inconsistencies around defining FRONTEND  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Inconsistencies around defining FRONTEND
List pgsql-hackers
Hi,

On 2022-08-23 19:50:00 -0400, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Tue, Aug 23, 2022 at 7:24 PM Andres Freund <andres@anarazel.de> wrote:
> >> Just to make sure I understand - you're just trying to get rid of the #define
> >> frontends, not the -DFRONTENDs passed in from the Makefile? Because afaics we
> >> still need those, correct?
> 
> > Oh, yeah, this only fixes the #define ones. But maybe fixing the other
> > ones with a similar approach would be possible?
> 
> > I really don't see why we should tolerate having #define FRONTEND in
> > more than once place.
> 
> src/port and src/common really need to do it like that (ie pass in
> the -D switch) so that the identical source file can be built
> both ways.  Maybe we could get rid of -DFRONTEND in other places,
> like pg_rewind and pg_waldump.

We could, if we make xlogreader.c and the rmgrdesc routines built as part of
src/common. I don't really see how otherwise.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: add checkpoint stats of snapshot and mapping files of pg_logical dir
Next
From: Andres Freund
Date:
Subject: Re: Symbol referencing errors