Hi, all, Markus Schaber schrieb:
> As a small workaround, I could imagine to add a small additional column > in the table that contains the geometry's bbox, and which I use the && > operator against. This should avoid touching the TOAST for the skipped rows. For your personal amusement: I just noticed that, after adding the additional column containing the bbox and running VACUUM FULL, the table now has a size of 4 pages, and that's enough for the query optimizer to choose an index scan. At least that saves us from modifying and redeploying a bunch of applications to use the && bbox query:-) Markus -- markus schaber | dipl. informatiker logi-track ag | rennweg 14-16 | ch 8001 zürich phone +41-43-888 62 52 | fax +41-43-888 62 53 mailto:[EMAIL PROTECTED] | www.logi-track.com
signature.asc
Description: OpenPGP digital signature
