Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date
Msg-id 15322.1262664181@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I think you're dismissing the idea too cavalierly.  If A generates B,
> A is inevitably changed frequently, but the changes to A affect B only
> rarely, this is a good trick.

The only output file that is unlikely to change is schemapg.h, which is
depended on by exactly one .c file.  It's a waste of time to try to
optimize this at all ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting