Received: from consumercontact.com ([209.167.202.12]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA53303 for ; Thu, 6 Jan 2000 14:43:25 -0500 (EST) (envelope-from rick@consumercontact.com) Received: from consumercontact.com ([192.168.1.54]) by consumercontact.com (8.8.7/8.8.7) with ESMTP id OAA18367; Thu, 6 Jan 2000 14:36:34 -0500 Message-ID: <3874F00D.F6A504B9@consumercontact.com> Date: Thu, 06 Jan 2000 14:42:05 -0500 From: Rick Delaney X-Mailer: Mozilla 4.61 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: Jan Wieck , pgsql-sql@postgreSQL.org Subject: Re: [SQL] Calculation dependencies in views References: <38728CE2.C1756D3E@consumercontact.com> <3872987B.C289AB59@debis.com> <3873A662.37B94F7E@consumercontact.com> <3873BC4C.3D4E4BCC@debis.com> <3873D036.5A2A9B18@consumercontact.com> <3873DD6E.BBBF5813@debis.com> <19740.947123224@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tom Lane wrote: > > Jan Wieck writes: > > > These two examples will result in exactly the same querytree after > > rewriting, if you SELECT from v1. The second needs two passes in the > > rewriter, but that's the only difference. > > Actually, there's another big difference: the stored rule plan string > for v1 in the second case is shorter than it is in the first case, > because the a+b additions don't show up as operator nodes in v1's > definition in the second case. (If the references to v1_sub were > flattened out before the rule were stored, it wouldn't take two passes > of rewriting to expand the rule. But they aren't, and it does ;-).) Interesting. Anyway, I grok it now. Thank you both for all your help. Cheers, --Rick