Hi, If spatial index is needed depends on the data. It is certainly needed when the table is large (million features or so) and requests typically cover a small area. If for example 1000 features gets selected it means that the spatial index can filter out 999 thousand features. If the table is small like one thousand features, then it is not so expensive to read everything without spatial filter.
You are giving us little by little more information. I do not believe that the PostgreSQL 13 vs version 11 is the main thing at all. However, I do not have databases hosted on AWS and I can not make tests in the similar environment that you have. -Jukka Rahkonen- Lähettäjä: MapServer-users <mapserver-users-boun...@lists.osgeo.org> Puolesta Rob Dennett via MapServer-users Lähetetty: tiistai 6. helmikuuta 2024 21.53 Vastaanottaja: mapserver-users@lists.osgeo.org Aihe: Re: [MapServer-users] Why is Mapserver slower in Postgres 13 than in Postgres 11? Both DBs are hosted on AWS Aurora. The old one is serverless v1 and the new one is serverless v2. We were thinking that perhaps the geom column for my table needed a spatial index even though the old db doesn't have one. Is that possible? Also, would it make sense that the same query run on both should take the same amount of time (roughly)? Thanks, Rob
_______________________________________________ MapServer-users mailing list MapServer-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
