It is all one table (20M+ records). But it has 16 columns. The main filter (WHERE) is the bbox column (a geometry column). But there are other columns such as image type, producer, and time that we also want to allow the user to use to downselect.
And as I said, between the type and the producer there are about 40 possible values. I also suspect that it might be wise to break the query into two. First doing the spatial selection (which should bring the table down to a few thousand entries) and then do a subsequent search on the type, producer, date, etc. Is this true, or is the PLANNER smart enough to do this? (Like I said, I a C.S. software guy, not a DB guy). -- View this message in context: http://postgis.17.n6.nabble.com/Very-large-WHERE-clause-tp4952906p4958314.html Sent from the PostGIS - User mailing list archive at Nabble.com. _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
