Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3BA94475F0D for ; Tue, 3 Sep 2002 00:06:05 -0400 (EDT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id C66AA475E32 for ; Tue, 3 Sep 2002 00:06:04 -0400 (EDT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id F1B2DD602; Mon, 2 Sep 2002 21:06:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id E76775C03; Mon, 2 Sep 2002 21:06:05 -0700 (PDT) Date: Mon, 2 Sep 2002 21:06:05 -0700 (PDT) From: Stephan Szabo To: Josh Berkus Cc: JOE , Subject: Re: union optimization in views In-Reply-To: <200208291052.39160.josh@agliodbs.com> Message-ID: <20020902210247.H41635-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/3 X-Sequence-Number: 9280 On Thu, 29 Aug 2002, Josh Berkus wrote: > Joe, > > > We are attempting to move a couple of systems from Oracle to Postgres but > can not do so without application rewrites due to the current use of views > with UNIONs and the criticality of the performances of these views. > > > > I was wondering if a decision has been made on the optimization with the > UNION clause in views. There are many documents in the SQL archive showing > that the "push down" is not occuring and thus the use of UNION's in views is > limited to case where the data set is small or performance is not a > consideration. I also looked through the TODO list and didn't see anything > (of course I could have missed references). > > I'd take this up on PGSQL-HACKERS. The UNION VIEW optimization, last I > checked, was stalled mainly because nobody wanted to work on it. Maybe you > can? Tom sent a patch to -patches against then cvs head that did union/intersect [all] push down last week. Unless someone comes up with a complaint, I'd guess that's going to make it in 7.3