This issue is caused by the usage of materialized view to store temporary results from filtering. This views are used to generate the vector tile of choropleth map (properties+province). My proposed solution is to switch to a standar view (not materialized one) in exchange of the speed when generating the vector tile.
On other hand, the generation of map session is too much, it's being generated when user goes to the map page. When the screen is refreshed, the session is regenerated and causing many materialized views are created in the database. We should store this session into the cookie/local storage, so the user can reuse it.
This issue is caused by the usage of materialized view to store temporary results from filtering. This views are used to generate the vector tile of choropleth map (properties+province). My proposed solution is to switch to a standar view (not materialized one) in exchange of the speed when generating the vector tile.
On other hand, the generation of map session is too much, it's being generated when user goes to the map page. When the screen is refreshed, the session is regenerated and causing many materialized views are created in the database. We should store this session into the cookie/local storage, so the user can reuse it.