It's possible to create an index on the transformed data without creating a
second table, though it you need to use the same transform often it might
be worth creating a second geometry column in the same table.
Postann - you are using LIKE queries - these are rarely fast. I would break
that
If you are transforming the geom in your query this could be the issue. I
prefer to create views in PG, rather than using GeoServer queries but I
believe it is essentially the same. If I create a PG view where I am
altering the geom, basically any st_ function or aggrigation, this results
in poor
Hi Team,
Thanks for your support.
Could someone please suggest on the below query.
One of the query which was created on GIS data is taking a long time and
even it is not taking the index as well. I have included all the required
details for reference.
Database Stack:
===
