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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date: 2010-01-05 04:03:01
Message-ID: 15322.1262664181@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

Responses

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

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