[postgis-users] Status of PostGIS 3 and PostgreSQL Yum Repos?

Paul Ramsey pramsey at cleverelephant.ca
Mon Nov 4 19:17:59 PST 2019


40x is shocking and it looks like the only difference is red hat 7 vs 8.?

> On Nov 4, 2019, at 6:47 PM, Daryl Herzmann <akrherz at gmail.com> wrote:
> 
> Thanks for the response Raúl,
> 
> I tried PostGIS 3.0 GA now on RHEL7 and am still seeing the same
> puzzling slow behaviour.  My RHEL8 development laptop crunches the
> same data through ST_Transform() in excellent time.  Here's a
> comparison of the explain analyze on both hosts
> 
> RHEL7
> 
> POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="120"
> GEOS="3.8.0-CAPI-1.13.1 " PROJ="6.2.0" LIBXML="2.9.1" LIBJSON="0.11"
> LIBPROTOBUF="1.0.2" WAGYU="0.4.3 (Internal)"
> 
> explain analyze select st_transform(geom, 2163) from stations;
>                                                             QUERY
> PLAN
> -------------------------------------------------------------------------------------------------------------------------------------
> Gather  (cost=1000.00..113124.15 rows=69980 width=32) (actual
> time=3535.920..4624.442 rows=70025 loops=1)
>   Workers Planned: 1
>   Workers Launched: 1
>   ->  Parallel Seq Scan on stations  (cost=0.00..105126.15 rows=41165
> width=32) (actual time=4061.506..4104.824 rows=35012 loops=2)
> Planning Time: 0.057 ms
> Execution Time: 4627.474 ms
> 
> 
> RHEL8
> 
> POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="120"
> GEOS="3.8.0-CAPI-1.13.1 " PROJ="6.2.0" LIBXML="2.9.7" LIBJSON="0.13.1"
> LIBPROTOBUF="1.3.0" WAGYU="0.4.3 (Internal)"
> 
> explain analyze select st_transform(geom, 2163) from stations;
>                                                           QUERY PLAN
> ---------------------------------------------------------------------------------------------------------------------------------
> Gather  (cost=1000.00..112529.32 rows=69618 width=32) (actual
> time=46.818..90.248 rows=69618 loops=1)
>   Workers Planned: 1
>   Workers Launched: 1
>   ->  Parallel Seq Scan on stations  (cost=0.00..104567.52 rows=40952
> width=32) (actual time=49.211..72.335 rows=34809 loops=2)
> Planning Time: 0.036 ms
> Execution Time: 91.871 ms
> 
> 
> I don't have an exact copy of the data between the two hosts, but it is close.
> 
> thanks
> daryl
> 
>> On Wed, Oct 30, 2019 at 8:58 AM <rmrodriguez at carto.com> wrote:
>> 
>> The are waiting for GDAL 3.0.2 to be out to package them together.
>> Source: https://twitter.com/DevrimGunduz/status/1189216750895882243
>> 
>> In any case, ST_Transform is slower because PROJ6 is slower, but it
>> shouldn't be that slow.
>> 
>>> On Wed, Oct 30, 2019 at 2:54 PM Daryl Herzmann <akrherz at gmail.com> wrote:
>>> 
>>> Greetings,
>>> 
>>> Does anybody know what's going on with the PostgreSQL Yum repos
>>> supporting PostGIS 3?  The repos continue to be stuck with 3.0 alpha4
>>> 
>>> https://yum.postgresql.org/12/redhat/rhel-7-x86_64/
>>> 
>>> I am having issues with performance with that alpha4 release and am
>>> hoping they magically go away with the GA release of version 3 :)
>>> 
>>> https://redmine.postgresql.org/issues/4826
>>> 
>>> Is there some public interface to see the build status results of these RPMs?
>>> 
>>> thanks
>>> daryl
>>> _______________________________________________
>>> postgis-users mailing list
>>> postgis-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>> 
>> 
>> 
>> --
>> Raúl Marín Rodríguez
>> carto.com
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users


More information about the postgis-users mailing list