[SCM] PostGIS branch master updated. 3.4.0rc1-1078-g3a9d2eb85

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, master has been updated
  discards  3e28490365b6fa77a9ce893aba90feff39cc72c1 (commit)
       via  3a9d2eb8503004e9496d25eeb00e0499b0e6afc2 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (3e28490365b6fa77a9ce893aba90feff39cc72c1)
            \
             N -- N -- N (3a9d2eb8503004e9496d25eeb00e0499b0e6afc2)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3a9d2eb8503004e9496d25eeb00e0499b0e6afc2
Author: Regina Obe <lr at pcorp.us>
Date:   Sat Mar 30 04:08:19 2024 -0400

    Fix regression issue on 32-bit
    and arm failures
    References #5704 for PostGIS 3.5.0

diff --git a/regress/core/geography_centroid.sql b/regress/core/geography_centroid.sql
index c8930d43b..260e4d32a 100644
--- a/regress/core/geography_centroid.sql
+++ b/regress/core/geography_centroid.sql
@@ -1,18 +1,19 @@
 
 -- check for pole crossing
-SELECT c, ST_Centroid(g::geography) FROM
+SELECT c, ST_AsText(ST_Centroid(g::geography),6) FROM
 ( VALUES
     ('geog_centroid_mpt_pole_north', 'MULTIPOINT ( 90 80, -90 80)'),
     ('geog_centroid_mpt_pole_south', 'MULTIPOINT ( 90 -80, -90 -80)')
 ) AS u(c, g);
 
 -- check for IDL crossing
-SELECT c, ST_Centroid(g::geography) FROM
+SELECT c,  ST_X(gc.geom)::numeric(12,6) AS x, ST_Y(gc.geom)::numeric(12,6) AS y
+FROM
 ( VALUES
     ('geog_centroid_mpt_idl_1', 'MULTIPOINT ( 179 0, -179 0)'),
     ('geog_centroid_mpt_idl_2', 'MULTIPOINT ( 178 0, -179 0)'),
     ('geog_centroid_mpt_idl_3', 'MULTIPOINT ( 179 0, -178 0)')
-) AS u(c, g);
+) AS u(c, g), geometry(ST_Centroid(g::geography)) AS gc(geom);
 
 -- point should return itself
 SELECT c, ST_Centroid(g::geography) FROM
diff --git a/regress/core/geography_centroid_expected b/regress/core/geography_centroid_expected
index 270eced12..b9e5ca7ca 100644
--- a/regress/core/geography_centroid_expected
+++ b/regress/core/geography_centroid_expected
@@ -1,8 +1,8 @@
-geog_centroid_mpt_pole_north|0101000020E610000000000000000000000000000000805640
-geog_centroid_mpt_pole_south|0101000020E6100000000000000000000000000000008056C0
-geog_centroid_mpt_idl_1|0101000020E610000000000000008066400000000000000000
-geog_centroid_mpt_idl_2|0101000020E610000000000000007066400000000000000000
-geog_centroid_mpt_idl_3|0101000020E610000000000000007066C00000000000000000
+geog_centroid_mpt_pole_north|POINT(0 90)
+geog_centroid_mpt_pole_south|POINT(0 -90)
+geog_centroid_mpt_idl_1|180.000000|0.000000
+geog_centroid_mpt_idl_2|179.500000|0.000000
+geog_centroid_mpt_idl_3|-179.500000|0.000000
 geog_centroid_pt_self_1|0101000020E610000000000000000010400000000000002040
 geog_centroid_pt_self_2|0101000020E61000000000000000002EC00000000000003040
 geog_centroid_pt_self_3|0101000020E610000000000000000037C000000000000045C0

-----------------------------------------------------------------------

Summary of changes:
 regress/core/geography_centroid.sql      | 5 +++--
 regress/core/geography_centroid_expected | 6 +++---
 2 files changed, 6 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
PostGIS