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

From Peter Eisentraut
Subject Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date
Msg-id 1262705479.21041.4.camel@fsopti579.F-Secure.com
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>)
List pgsql-hackers
On mån, 2010-01-04 at 22:54 -0500, Robert Haas wrote:
> 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. 

If that is the case, you might want to consider splitting up A or
refactoring B so you don't have so many useless dependencies.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: execute sql commands in core
Next
From: Tom Lane
Date:
Subject: Re: Does parallel make require guards against duplicate actions?