Robert Haas <robertmhaas(at)gmail(dot)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

In response to

• Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting at 2010-01-05 03:54:20 from Robert Haas

Responses

• Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting at 2010-01-05 04:03:48 from Robert Haas

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2010-01-05 04:03:48
	Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Previous:	From: Alvaro Herrera	Date: 2010-01-05 03:57:33
	Subject: Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

pgsql-committers by date

Next:	From: Robert Haas	Date: 2010-01-05 04:03:48
	Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Previous:	From: Alvaro Herrera	Date: 2010-01-05 03:57:33
	Subject: Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting