On Sun, 25 Jul 1999, Tom Lane wrote:
> > At 23:45 +0300 on 23/07/1999, John M. Flinchbaugh wrote:
> >> [ how to avoid "rule plan string too big" ? ]
> He might have some luck by splitting the query into two subqueries,
> one that joins half the tables and the other one joining the other half,
> then a top query that joins those two. (The trick here is figuring
> out how to split the tables into two groups that can be joined without
> reference to the other group and without producing too many useless
> tuples.) The top query is still going to be tight, because the number
> of targetlist nodes (output columns) won't change, but reducing the
> number of tables it references to two views and simplifying its WHERE
> condition down to one or so clauses will both help eliminate nodes.
i broke that huge view into a bunch of smaller ones successfully, but the
top view which pulled together 2 smaller views (which each pulled together
smaller parts,etc), and i got the same error. it seems to still get hung
up on the number of columns the view was returning, so i had to drop a few
of the less useful columns to get it to create the view successfully.
____________________}John Flinchbaugh{______________________
| -> glynis@hjsoft.com <- john@cs.millersv.edu |
| glynis@netrax.net http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
