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

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date
Msg-id 603c8f071001042003k77fe55a1u28624fcb37101443@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jan 4, 2010 at 11:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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 ...

OK, fair enough.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Next
From: Robert Haas
Date:
Subject: Re: quoting psql varible as identifier