Skip site navigation (1) Skip section navigation (2)

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:48
Message-ID: 603c8f071001042003k77fe55a1u28624fcb37101443@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Mon, Jan 4, 2010 at 11:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 ...

OK, fair enough.

...Robert

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-05 04:12:55
Subject: Re: quoting psql varible as identifier
Previous:From: Tom LaneDate: 2010-01-05 04:03:01
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

pgsql-committers by date

Next:From: Tom LaneDate: 2010-01-05 06:41:44
Subject: pgsql: Further code review for genbki.pl.
Previous:From: Tom LaneDate: 2010-01-05 04:03:01
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group