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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date: 2010-01-05 15:31:19
Message-ID: 1262705479.21041.4.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers 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.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Meskes 2010-01-05 16:38:23 pgsql: Applied patch by Boszormenyi Zoltan <zb@cybertec.at> to add sqlda
Previous Message User Mpihlak 2010-01-05 14:49:57 plproxy - plproxy: Regression tests for SQL/MED.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-05 15:38:41 Re: Does parallel make require guards against duplicate actions?
Previous Message Tom Lane 2010-01-05 15:29:44 Re: execute sql commands in core