[postgis-users] Problem with Nested Loop in a query with postgis
Regina Obe
lr at pcorp.us
Mon Jul 24 20:29:22 PDT 2023
Anderson,
Thanks. That all makes more sense now.
So when you were running 3.1.7 on PostgreSQL 10 things were still good right?
And it was when you ran on PG14
SELECT postgis_extensions_upgrade();
Is when your plans went south. That explains a lot.
The main difference between the 3.1 scripts < PG 12 and PostGIS 3.1+ > PG 12 is we changed many of the indexable functions like ST_DWithin to use the new index instrumentation which allowed us to provide more accurate costs for the functions. So the function itself is also different in the costing and its syntax.
Without the SELECT postgis_extensions_upgrade();
You are running with scripts that use the non-instrumentation versions of the function definitions and have no meaningful costs on those functions to allow the indexes to be used.
Hopefully it’s just the costs at fault here.
For PG < 12, The HIGH COST was set to 10 and for 12 and above was set to 10000
Legend
#if POSTGIS_PGSQL_VERSION >= 120
#define _COST_DEFAULT COST 1
#define _COST_LOW COST 50
#define _COST_MEDIUM COST 500
#define _COST_HIGH COST 10000
#else
#define _COST_DEFAULT COST 1
#define _COST_LOW COST 1
#define _COST_MEDIUM COST 10
#define _COST_HIGH COST 10
#endif
I would try switching the cost on your ST_Transform function and ST_DWithin geography functions back to 10 and see if that sets things back.
Something like below, but change the schema public to the schema you currently have PostGIS installed
CREATE OR REPLACE FUNCTION public.st_transform(
geometry,
integer)
RETURNS geometry
LANGUAGE 'c'
COST 10
IMMUTABLE STRICT PARALLEL SAFE
AS '$libdir/postgis-3', 'transform';
CREATE OR REPLACE FUNCTION public.st_dwithin(
geog1 geography,
geog2 geography,
tolerance double precision,
use_spheroid boolean DEFAULT true)
RETURNS boolean
LANGUAGE 'c'
COST 5000
IMMUTABLE STRICT PARALLEL SAFE SUPPORT public.postgis_index_supportfn
AS '$libdir/postgis-3', 'geography_dwithin';
If that works, try setting them to 5000 and see if that still works.
As a general rule, I try to avoid nesting ST_Transform calls in indexable functions.
I think we did have this issue reported, and in 3.4, we lowered the costing of High cost to 5000.
Instigated by this observation https://lists.osgeo.org/pipermail/postgis-devel/2022-September/029818.html
Which appears to be similar to what you are suffering.
I think we didn’t backport the change, cause we weren’t confident in our new costing.
Hope that helps,
Regina
From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf Of Anderson Mallmann
Sent: Monday, July 24, 2023 10:33 PM
To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
Subject: Re: [postgis-users] Problem with Nested Loop in a query with postgis
Hi
I restored the backup from pg10 2.5.3 and updated postis to 3.1.7. After that I upgrade postgres to pg14.
I think that in the first message plan, we forgot to run postgis_extensions_upgrade in pg14 3.1.7, because now I tested the query before and after the postgis upgrade, and the plan changed. That explains the difference from 3.1.7 and 3.1.8.
-------------------------------------------------------------------
postgis_full_version | POSTGIS="2.5.3 r17699" [EXTENSION] PGSQL="100" GEOS="3.8.1-CAPI-1.13.3" PROJ="Rel. 7.0.1, May 1st, 2020" GDAL="GDAL 3.0.4, released 2020/01/28 GDAL_DATA not found" LIBXML="2.9.1" LIBJSON="0.11" LIBPROTOBUF="1.0.2" RASTER
version | PostgreSQL 10.23 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
Nested Loop (cost=4.92..12.04 rows=1 width=263) (actual time=190.398..459.920 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 15, 0))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Buffers: shared hit=1340
-> Unique (cost=4.64..4.65 rows=1 width=3) (actual time=189.532..189.535 rows=1 loops=1)
Output: s.state, ((s.state)::text)
Buffers: shared hit=478
-> Sort (cost=4.64..4.64 rows=1 width=3) (actual time=189.531..189.533 rows=1 loops=1)
Output: s.state, ((s.state)::text)
Sort Key: ((s.state)::text)
Sort Method: quicksort Memory: 25kB
Buffers: shared hit=478
-> Index Scan using states_geography_idx on region.states s (cost=0.14..4.63 rows=1 width=3) (actual time=188.775..189.492 rows=1 loops=1)
Output: s.state, s.state
Index Cond: (geography(st_transform(s.geom, 4326)) && '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography)
Filter: (('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography && _st_expand(geography(st_transform(s.geom, 4326)), '15000'::double precision)) AND _st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true))
Rows Removed by Filter: 1
Buffers: shared hit=475
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.28..4.78 rows=1 width=4835) (actual time=0.631..141.758 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, pols.last_updated
Index Cond: ((geography(pols.geom) && '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography) AND ((pols.details ->> 'state'::text) = (s.state)::text))
Filter: (((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision) AND ('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography && _st_expand(geography(pols.geom), '15000'::double precision)) AND _st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true))
Rows Removed by Filter: 395
Buffers: shared hit=862
Planning time: 27.886 ms
Execution time: 460.116 ms
-------------------------------------------------------------------
postgis_full_version | POSTGIS="3.1.7 aafe1ff" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" PROJ="7.2.1" GDAL="GDAL 3.3.3, released 2021/10/25" LIBXML="2.9.1" LIBJSON="0.11" RASTER
version | PostgreSQL 10.23 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
Merge Semi Join (cost=15.83..16.04 rows=1 width=263) (actual time=601.348..652.897 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 9, 8))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Merge Cond: (((pols.details ->> 'state'::text)) = (s.state)::text)
Buffers: shared hit=1255 read=1881
-> Sort (cost=4.49..4.50 rows=1 width=4835) (actual time=328.831..328.878 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, ((pols.details ->> 'state'::text))
Sort Key: ((pols.details ->> 'state'::text))
Sort Method: quicksort Memory: 1314kB
Buffers: shared hit=1168 read=909
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.28..4.48 rows=1 width=4835) (actual time=9.944..328.144 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, (pols.details ->> 'state'::text)
Index Cond: (geography(pols.geom) && '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography)
Filter: (('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography && _st_expand(geography(pols.geom), '15000'::double precision)) AND _st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true) AND ((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision))
Rows Removed by Filter: 395
Buffers: shared hit=1162 read=909
-> Sort (cost=11.34..11.36 rows=9 width=3) (actual time=272.386..272.386 rows=1 loops=1)
Output: s.state
Sort Key: s.state
Sort Method: quicksort Memory: 25kB
Buffers: shared hit=87 read=972
-> Seq Scan on region.states s (cost=0.00..11.19 rows=9 width=3) (actual time=173.108..272.375 rows=1 loops=1)
Output: s.state
Filter: st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true)
Rows Removed by Filter: 26
Buffers: shared hit=87 read=972
Planning time: 2.386 ms
Execution time: 653.027 ms
*before run postgis_extensions_upgrade
-------------------------------------------------------------------
postgis_full_version | POSTGIS="3.1.7 aafe1ff" [EXTENSION] PGSQL="100" (procs need upgrade for use with PostgreSQL "140") GEOS="3.9.2-CAPI-1.14.3" PROJ="7.2.1" GDAL="GDAL 3.3.3, released 2021/10/25" LIBXML="2.9.1" LIBJSON="0.11" RASTER
version | PostgreSQL 14.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
Merge Semi Join (cost=287.90..289.79 rows=1 width=328) (actual time=511.157..565.637 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 9, 8))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Merge Cond: (((pols.details ->> 'state'::text)) = (s.state)::text)
Buffers: shared hit=1275 read=1873 dirtied=1
-> Sort (cost=4.49..4.50 rows=1 width=328) (actual time=236.170..236.214 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, ((pols.details ->> 'state'::text))
Sort Key: ((pols.details ->> 'state'::text))
Sort Method: quicksort Memory: 1314kB
Buffers: shared hit=1184 read=901 dirtied=1
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.29..4.48 rows=1 width=328) (actual time=9.117..234.960 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, (pols.details ->> 'state'::text)
Index Cond: (geography(pols.geom) && '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography)
Filter: (('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography && _st_expand(geography(pols.geom), '15000'::double precision)) AND _st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true) AND ((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision))
Rows Removed by Filter: 395
Buffers: shared hit=1178 read=901 dirtied=1
-> Sort (cost=283.41..283.99 rows=233 width=12) (actual time=274.853..274.853 rows=1 loops=1)
Output: s.state
Sort Key: s.state
Sort Method: quicksort Memory: 25kB
Buffers: shared hit=91 read=972
-> Seq Scan on region.states s (cost=0.00..274.25 rows=233 width=12) (actual time=174.226..274.842 rows=1 loops=1)
Output: s.state
Filter: st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true)
Rows Removed by Filter: 26
Buffers: shared hit=91 read=972
Query Identifier: -3917083104069499193
Planning:
Buffers: shared hit=441 read=27
Planning Time: 2.431 ms
Execution Time: 566.361 ms
*after run postgis_extensions_upgrade
-------------------------------------------------------------------
postgis_full_version | POSTGIS="3.1.7 aafe1ff" [EXTENSION] PGSQL="140" GEOS="3.9.2-CAPI-1.14.3" PROJ="7.2.1" GDAL="GDAL 3.3.3, released 2021/10/25" LIBXML="2.9.1" LIBJSON="0.11" RASTER
version | PostgreSQL 14.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
Nested Loop Semi Join (cost=0.68..111.51 rows=1 width=328) (actual time=155.732..55359.680 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 9, 8))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Join Filter: ((pols.details ->> 'state'::text) = (s.state)::text)
Buffers: shared hit=73020
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.41..55.77 rows=1 width=328) (actual time=0.158..195.166 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, pols.last_updated
Index Cond: (geography(pols.geom) && _st_expand('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision))
Filter: (st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true) AND ((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision))
Rows Removed by Filter: 395
Buffers: shared hit=836
-> Index Scan using states_geography_idx on region.states s (cost=0.27..54.38 rows=1 width=12) (actual time=132.415..132.415 rows=1 loops=416)
Output: s.state_code, s.state, s.country, s.geom
Index Cond: (geography(st_transform(s.geom, 4326)) && _st_expand('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision))
Filter: st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true)
Rows Removed by Filter: 1
Buffers: shared hit=71136
Query Identifier: -3917083104069499193
Planning Time: 0.360 ms
Execution Time: 55360.033 ms
Thanks,
Anderson
Em sex., 21 de jul. de 2023 às 01:37, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > escreveu:
Was this upgrading pg10 from 2.5.3 to 3.0.7?
I’m more interested in seeing this run in newer PostgreSQL from 12 on.
There was a lot of stuff that changed in PostgreSQL 12 that affects planner behavior.
Any chance you can recompare your PG 14 3.1.7 vs. 3.1.8?
The change detailed between 3.1.7 and 3.1.8 did not make any sense to us as nothing in the change log between those two versions would account for the issue you are describing here.
Or was that a typo and the issue was between 3.0.7 and 3.1.8? Planner changes between 3.0.7 and 3.1.8 is more likely.
As mentioned, it would really help if when you state your versions, you provide output of
SELECT postgis_full_version(), version();
Even micro differences between PostgreSQL versions have on rare occasions affected planner behavior too.
Thanks,
Regina
From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org <mailto:postgis-users-bounces at lists.osgeo.org> ] On Behalf Of Anderson Mallmann
Sent: Thursday, July 20, 2023 5:13 PM
To: PostGIS Users Discussion <postgis-users at lists.osgeo.org <mailto:postgis-users at lists.osgeo.org> >
Subject: Re: [postgis-users] Problem with Nested Loop in a query with postgis
I restored a backup of this database in pg10 2.5.3 and updated postgis to 3.0.7, at first the query used the Merge Semi Join and the performance was fine, so I force to use Nested Loop and perforce was dropped.
So i think our problem was that postgres changed the plan for this query and st_dwithin(geography, geography) in loop didn't perform well, but I still don't understand why postgres is choosing to run this query with Nested Loop.
I did other tests with a subset of the data and with a similar query using nested loop the performance was not good in 2.5 or 3.0.
I uploaded the subset to this repository https://github.com/aamallmann/postgis-region-db if you want to test.
Em seg., 17 de jul. de 2023 às 16:40, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > escreveu:
I looked at our list of items between 3.1.7 and 3.1.8
https://git.osgeo.org/gitea/postgis/postgis/src/branch/stable-3.1/NEWS
and can’t find any that would cause what you describe below.
It’s possible whatever was changed we didn’t consider strong enough to put in the news.
I haven’t checked the git repo yet to see what changed.
Usually these switches in plans are often triggered by changes in costs of the functions or just data and it is possible we adjusted some of the costs on these functions.
I was thinking the 10 to 14 switch might have been caused by the function instrumentation changes.
But that wouldn’t explain your experiencing the same issue on 14 3.1.7 vs 14 3.1.8
If you still have both running, can you give us the output
SELECT postgis_full_version(), version();
So we can confirm we are truly comparing only a difference in PostGIS version and not the libraries used or PostgreSQL minor version.
Thanks,
Regina
From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org <mailto:postgis-users-bounces at lists.osgeo.org> ] On Behalf Of Anderson Mallmann
Sent: Monday, July 17, 2023 10:23 AM
To: postgis-users at lists.osgeo.org <mailto:postgis-users at lists.osgeo.org> ; lviecelli199 at gmail.com <mailto:lviecelli199 at gmail.com> ; torres.glauco at gmail.com <mailto:torres.glauco at gmail.com>
Subject: [postgis-users] Problem with Nested Loop in a query with postgis
Hi,
Here at the company I work for, we upgraded a postgres database from version 10 to 14 and postgis 2.5.3 to 3.3.3 and in a specific query we noticed a huge performance decrease between these versions. This query was running less than 1s and now it takes more than 50s.
Now we are trying to figure out what the real problem is and in which version this started to happen. Some of our discoveries so far:
1) The query runs fine until postgis 3.1.7
2) In postgis 3.1.8 the query execution changed from Merge Semi Join to Nested Loop Semi Join.
3) Running this query on postgis >= 3.1.8 disabling nested loop with “set enable_nestloop = false” the query runs as before without any problem.
We don’t know why the plan changed in postgis >= 3.1.8 to use Nested Loop, but even in earlier versions if any query like this uses nested loop, the performance drops.
Query:
SELECT pols.pol_id, pols.type, kml, json_build_object('type', 'Feature', 'geometry', st_asgeojson(pols.geom)::jsonb) as geoJson, pols.status pol_status, pols.owner_id pol_owner, pols.details, pols.creation_date as pol_creation_date, pols.country as country, pols.state as state, pols.city as city, pols.label as label FROM polygons pols WHERE pols.owner_id is null AND pols.status = 'ACTIVE' AND pols.type in ('REGION') AND pols.details->>'state' in (SELECT s.state FROM states s WHERE ST_DWITHIN(Geography(ST_Transform(s.geom,4326)), ST_GeographyFromText('POINT(-43.113826 -22.9022)'),'15000')) AND (ST_DWithin(ST_GeographyFromText('POINT(-43.113826 -22.9022)'), Geography(pols.geom),'15000')) AND (ST_MaxDistance(ST_GeomFromText('POINT(-43.113826 -22.9022)', 4326), pols.geom) * 111195) <= '15000'
Here are the explains for this query:
pg 14 - postgis 3.1.7
Merge Semi Join (cost=15.83..16.04 rows=1 width=263) (actual time=529.041..586.241 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 9, 8))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Merge Cond: (((pols.details ->> 'state'::text)) = (s.state)::text)
Buffers: shared hit=3193
-> Sort (cost=4.49..4.50 rows=1 width=4656) (actual time=244.333..244.367 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, ((pols.details ->> 'state'::text))
Sort Key: ((pols.details ->> 'state'::text))
Sort Method: quicksort Memory: 1314kB
Buffers: shared hit=2131
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.28..4.48 rows=1 width=4656) (actual time=10.207..243.079 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, (pols.details ->> 'state'::text)
Index Cond: (geography(pols.geom) && '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography)
Filter: (('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography && _st_expand(geography(pols.geom), '15000'::double precision)) AND _st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true) AND ((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision))
Rows Removed by Filter: 395
Buffers: shared hit=2125
-> Sort (cost=11.34..11.36 rows=9 width=3) (actual time=284.570..284.570 rows=1 loops=1)
Output: s.state
Sort Key: s.state
Sort Method: quicksort Memory: 25kB
Buffers: shared hit=1062
-> Seq Scan on region.states s (cost=0.00..11.19 rows=9 width=3) (actual time=180.759..284.564 rows=1 loops=1)
Output: s.state
Filter: st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true)
Rows Removed by Filter: 26
Buffers: shared hit=1062
Query Identifier: -6178717669455780324
Planning:
Buffers: shared hit=481
Planning Time: 31.139 ms
Execution Time: 586.869 ms
-----------
pg 14 - postgis 3.1.8
Nested Loop Semi Join (cost=0.67..111.50 rows=1 width=263) (actual time=179.622..59918.477 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, json_build_object('type', 'Feature', 'geometry', (st_asgeojson(pols.geom, 9, 8))::jsonb), pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label
Join Filter: ((pols.details ->> 'state'::text) = (s.state)::text)
Buffers: shared hit=72116 read=1075
-> Index Scan using polygons_geography_state_idx on region.polygons pols (cost=0.41..55.77 rows=1 width=4656) (actual time=9.477..221.758 rows=416 loops=1)
Output: pols.pol_id, pols.type, pols.kml, pols.geom, pols.status, pols.owner_id, pols.details, pols.creation_date, pols.country, pols.state, pols.city, pols.label, pols.last_updated
Index Cond: (geography(pols.geom) && _st_expand('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision))
Filter: (st_dwithin('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, geography(pols.geom), '15000'::double precision, true) AND ((_st_maxdistance('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geometry, st_convexhull(pols.geom)) * '111195'::double precision) <= '15000'::double precision))
Rows Removed by Filter: 395
Buffers: shared hit=269 read=692
-> Index Scan using states_geography_idx on region.states s (cost=0.26..54.37 rows=1 width=3) (actual time=142.676..142.676 rows=1 loops=416)
Output: s.state_code, s.state, s.country, s.geom
Index Cond: (geography(st_transform(s.geom, 4326)) && _st_expand('0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision))
Filter: st_dwithin(geography(st_transform(s.geom, 4326)), '0101000020E61000009EB7B1D9918E45C082734694F6E636C0'::geography, '15000'::double precision, true)
Rows Removed by Filter: 1
Buffers: shared hit=70988 read=171
Query Identifier: -6178717669455780324
Planning:
Buffers: shared hit=401 read=45
Planning Time: 30.729 ms
Execution Time: 59919.343 ms
Regards,
Anderson M.
_______________________________________________
postgis-users mailing list
postgis-users at lists.osgeo.org <mailto:postgis-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
postgis-users at lists.osgeo.org <mailto:postgis-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230724/5aa0a5d4/attachment.htm>
More information about the postgis-users
mailing list