For --auto-bounds quick, use ST_EstimatedExtent instead of ST_Extent for quicker results

[nyurik]

Modify PG querying to use a quicker extent function when the bound check is set to quick

Implementation is easy: simply add another bool param to calc_bounds, and use a different function depending on that param

martin/martin/src/pg/query_tables.rs

Line 214 in e304678

async fn calc_bounds(

[sharkAndshark]

martin/martin/src/pg/query_tables.rs

Line 228 in e304678

WHEN (SELECT ST_GeometryType(rb) FROM real_bounds LIMIT 1) = 'ST_Point'

I'm a little bit confused. Could ST_SetSRID(ST_GeometryType(ST_EXTENT(geom)),srid) be st_point? Seems always St_Polygon?

[nyurik]

@sharkAndshark this was done in #300 by @HackJack-101 a while ago, addressing bug #299. I may need to dig deeper though to understand why it was done

[sharkAndshark]

I made a test on a point table which has only one point. And seems that St_EstimatedExtent has fixed it. @nyurik

SELECT
	st_geometrytype ( ST_SetSRID ( ST_Extent ( geom ), 4544 ) ) AS type1,
	st_geometrytype ( ST_Extent ( geom ) ) AS type2 ,
	st_geometrytype(  ST_EstimatedExtent('public','project_copy1','geom')) as type3
FROM
	project_copy1
-- 	type1: ST_Point  type2: ST_Point   type3: ST_Polygon