Try to reduce the sql to this:
SELECT "table_name_id",
"ug_route_sub_type",
"sw_uid22",
encode(ST_AsBinary(ST_Simplify(ST_Force2D("the_geom"),
0.026540849041691673, true)),'base64') as "the_geom"
FROM "schema"."table_name"
WHERE
("the_geom" && ST_GeomFromText('POLYGON
Hi Giuseppe,
Thanks a lot for your quick response.
Regards,
PostgAnn.
On Fri, May 22, 2020 at 2:20 PM Giuseppe Broccolo
wrote:
> Hi PostgAnn,
>
> Why do you think bitmap heap scan is an issue? Checking the EXPLAIN
> ANALYSE of the query, looks like the planner uses
> the proper plan to execute
Hi PostgAnn,
Why do you think bitmap heap scan is an issue? Checking the EXPLAIN ANALYSE
of the query, looks like the planner uses
the proper plan to execute the query (the order of magnitude of expected
fetched rows and actual fetched after the execution
is mostly the same). In fact, the index is
Hi Team,
Thanks for your support.
We are using below environment:
*Application :*
=
Programming Language : JAVA
Geoserver
Database Stack:
===
PostgreSQL : 9.5.15
Postgis
We have 3 geoserver queries and are getting some performance issues.
The index has been created on g
