[postgis-devel] automatic BVOL on spatial columns

[Paul Ramsey]

If your only/main worry is that we are taking away configurability from 
the user, then you should cease worrying. Too much configurability can 
be a *bad* thing, in the hands of people who do not want to have it. It 
forces them to make a bunch of decisions about things that they really 
do not want to know about, right away when they are still trying to 
learn basic things about the software.

What we want is a default configuration that "works pretty good", and 
without *any* special knowledge or configuration on the part of the user 
about abstract things like bbox caching strategies and their consequences.

If we make configurable caching a compile-time option or "special fiddly 
runtime" option, we can document how to use it, and the 1% of users who 
want to wring every last drop of performance out of their installations 
can read it and figure how to use it.

The rest will not know, will not care, and will live longer happier lives.

Paul

strk at refractions.net wrote:
>>Also, this logic should be left to the user, so she can decide when to
>>cache and when not to. She might want fast load and successive
>>bbox caching, she might want to cache bbox only on indexed tables,
>>or only for geoms with npoints > X in a table and > Y in another.
>>
>>I just don't see an easy way though :(