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

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 (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-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

pgsql-hackers by date

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

pgsql-committers by date

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

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