[postgis-tickets] [SCM] PostGIS branch master updated. 3.3.0rc2-749-g1f6327f7c

[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
       via  1f6327f7caa84c093cfec900c433b44aba02a0ab (commit)
      from  705fc8743543779e6d74014a681249e0ccbdc129 (commit)

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 1f6327f7caa84c093cfec900c433b44aba02a0ab
Author: Sandro Santilli <strk at kbt.io>
Date:   Thu May 4 18:49:43 2023 +0200

    Tweak the interrupt test for ST_Segmentize to avoid early exit
    
    There's a new check in ST_Segmentize to avoid too many segments,
    I found a max length parameter which is still able to trigger
    interruption on my system.

diff --git a/regress/core/interrupt.sql b/regress/core/interrupt.sql
index e44c760c9..57e1ddea4 100644
--- a/regress/core/interrupt.sql
+++ b/regress/core/interrupt.sql
@@ -23,7 +23,7 @@ $$ LANGUAGE 'plpgsql' VOLATILE;
 
 SET statement_timeout TO 100;
 -- would run for many seconds if uninterruptible...
-SELECT ST_Segmentize(ST_MakeLine(ST_Point(4,39), ST_Point(1,41)), 1e-100);
+SELECT 'segmentize', ST_NPoints(ST_Segmentize(ST_MakeLine(ST_Point(4,39), ST_Point(1,41)), 1e-8));
 SELECT _timecheck('segmentize', '250ms');
 SET statement_timeout TO 0;
 -- Not affected by old timeout

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

Summary of changes:
 regress/core/interrupt.sql | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
PostGIS