On Mon, Aug 17, 2015 at 12:06:42PM +0200, Andres Freund wrote:
> On 2015-08-16 03:31:48 -0400, Noah Misch wrote:
> I'd love to make it a #warning intead of an error, but unfortunately
> that's not standard C :(
Okay.
> > Other than that benefit, making headers #error-on-FRONTEND mostly lets
> > us congratulate ourselves for having introduced the start of a header
> > layer distinction. I'd be for that if PostgreSQL were new, but I
> > can't justify doing it at the user cost already apparent. That would
> > be bad business.
>
> To me that's basically saying that we'll never ever have any better
> separation between frontend/backend headers since each incremental
> improvement won't be justifiable.
Exactly. This is one of those proposals that can never repay its costs.
Header refactoring seduces hackers, but the benefits don't materialize.
