Re: Union View Optimizer Creates Temp Table

Brian Foster wrote: > Hi, > > I have gathered from previous posts, that the optimizer will not create a > temp table to process a view if it does not have to eliminate duplicates > (union all). I have not found that to be the case. Can anyone shed some > light on this? The example below is a very simple case. It's probably far TOO simple. With so few records, and no filter, you are likely to skip all indexes in favour of sequential scans. > My production > tables have several million rows (A & B) and the view is an unusable pig. I > am running 9.20 UC3. Can we see the query plan for the real query then? Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+ sending to informix-list