* Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> FWIW, the PostGIS folks would *really* love to have a TABLESAMPLE which
> worked with geographic indexes. This would be tremendously useful for
> constructing low-resolution "zoom out" tiles on maps and similar.
I'm familiar with the concept of 'zoom out' tiles and PostGIS, but I
don't actually see the connection between that and TABLESAMPLE. Perhaps
I'm missing something, but I've never seen a case where you create 'zoom
out' tiles by just grabbing some portion of the data at random, as that
would end up creating empty spots or missing pieces.
My experience has been with running an algorithm on each record in the
data set to reduce the number of points on a given record (which ends up
reducing the size of the record, etc). You could also filter out
records which wouldn't be visible due to the small 'size' of the record.
Again, neither of those would benefit from a TABLESAMPLE command.
Perhaps they're thinking it's going to use a GIST index to only pull out
records matching a certain condition..? Except we have WHERE for that..
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-04-17 20:33:37|
|Subject: Re: Parameterized-path cost comparisons need some work |
|Previous:||From: Greg Stark||Date: 2012-04-17 20:27:55|
|Subject: Re: patch submission: truncate trailing nulls from heap rows to
reduce the size of the null bitmap|