| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Raising our compiler requirements for 9.6 |
| Date: | 2015-08-18 05:59:30 |
| Message-ID: | 20150818055930.GC2129613@tornado.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2015-08-18 07:08:43 | Re: checkpointer continuous flushing |
| Previous Message | Noah Misch | 2015-08-18 05:57:43 | Re: Test code is worth the space |