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

From Robert Haas
Subject Re: Inconsistencies around defining FRONTEND
Date
Msg-id CA+TgmoZZ3n5-RB83e8oC7BJW9DuGSCXe+1cB0ApqNV80FZqkbw@mail.gmail.com
Whole thread Raw
In response to Inconsistencies around defining FRONTEND  (Andres Freund <andres@anarazel.de>)
Responses Re: Inconsistencies around defining FRONTEND
Re: Inconsistencies around defining FRONTEND
List pgsql-hackers
On Sat, Aug 20, 2022 at 3:46 PM Andres Freund <andres@anarazel.de> wrote:
> Unfortunately, the remaining uses of FRONTEND are required. That's:
> - pg_controldata, via #define
> - pg_resetwal, via #define
> - pg_rewind, via -DFRONTEND, due to xlogreader.c
> - pg_waldump, via #define and -DFRONTEND, due to xlogreader.c, xlogstats.c, rmgrdesc/*desc.c

Actually, I think we could fix these pretty easily too. See attached.

This has been annoying me for a while. I hope we can agree on a way to
clean it up.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Move NON_EXEC_STATIC from c.h
Next
From: Nikita Glukhov
Date:
Subject: Re: SQL/JSON features for v15