[postgis-devel] PostGIS 3.2.0beta3 is released
Regina Obe
lr at pcorp.us
Wed Dec 8 15:25:01 PST 2021
Greg,
Any chance you can get us a gdb backtrace of this. Unless Paul can guess.
Hard to tell where it is breaking with this limited info.
I know geography interacts with proj so could be something messed up in the
proj interaction.
I would like to get an rc1 out soon but want to make sure this isn't a
serious issue you have uncovered before we do that.
Thanks,
Regina
> -----Original Message-----
> From: Greg Troxel [mailto:gdt at lexort.com]
> Sent: Saturday, December 4, 2021 8:44 PM
> To: Regina Obe <lr at pcorp.us>
> Cc: 'PostGIS Development Discussion' <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] PostGIS 3.2.0beta3 is released
>
>
> "Regina Obe" <lr at pcorp.us> writes:
>
> > Source:
> > https://download.osgeo.org/postgis/source/postgis-3.2.0beta3.tar.gz
>
> I locally updated the pkgsrc postgis entry and it built and packaged OK,
after
> removing the LDFLAGS patch I submitted upstream (thanks)
> adjusting the set of SQL upgrade files (normal)
>
> I ran tests on NetBSD 9 amd64 against postgresq1 10, the version I have
> installed (for no good reason), even though I intend to move to 12 for
semi-
> production use.
>
> Note that I have gdal 3.4.0, which while a release feels bleeding edge.
> I have not committed this to pkgsrc. I also have old proj 6.3.2, only
because I
> haven't gotten around to dealing with the brave new world of different
proj-
> data and network access. But gdal and proj work fine with qgis, as far as
I can
> tell, as does my postgis 3.1.4 installation.
>
> Note also that 3.1.4 is installed, and I am testing 3.2.0beta3 from the
build tree.
>
>
> My memory of previous version tests is that they basically work, except
there is
> a raster crash, which has been happening for a long time. This time, I
got a crash
> in geography:
>
> PostgreSQL 10.18 on x86_64--netbsd, compiled by gcc (nb3 20190319) 7.4.0,
> 64-bit
> Postgis 3.2.0beta3 - (1a89e36) - 2021-12-05 01:26:39
> scripts 3.2.0beta3 1a89e36
> raster scripts 3.2.0beta3 1a89e36
> GEOS: 3.10.1-CAPI-1.16.0
> PROJ: 6.3.2
> GDAL: GDAL 3.4.0, released 2021/11/04
>
> Running tests
>
> after-create-script
/tmp/work/databases/postgresql-postgis2/work/postgis-
> 3.2.0beta3/regress/hooks/hook-after-create.sql .. ok
> ./regress/core/affine .. ok in 63 ms
> ./regress/core/bestsrid .. ok in 56 ms
> ./regress/core/binary .. ok in 78 ms
> ./regress/core/boundary .. ok in 55 ms
> ./regress/core/chaikin .. ok in 55 ms
> ./regress/core/filterm .. ok in 54 ms
> ./regress/core/cluster .. ok in 67 ms
> ./regress/core/concave_hull .. ok in 216 ms
> ./regress/core/ctors .. ok in 55 ms
> ./regress/core/curvetoline .. ok in 54 ms
> ./regress/core/dump .. ok in 56 ms
> ./regress/core/dumppoints .. ok in 56 ms
> ./regress/core/dumpsegments .. ok in 55 ms
> ./regress/core/empty .. ok in 63 ms
> ./regress/core/estimatedextent .. ok in 118 ms
> ./regress/core/forcecurve .. ok in 54 ms
> ./regress/core/flatgeobuf .. ok in 70 ms
> ./regress/core/geography ..Died at /tmp/work/databases/postgresql-
> postgis2/work/postgis-3.2.0beta3/regress/run_test.pl line 744.
> failed (psql exited with an error: /tmp/pgis_reg/test_19_out)
>
> and test_19_out, timestamp 20:31:28 2021
>
> psql:geography.sql:11: server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> psql:geography.sql:11: connection to server was lost
>
> The end of regress_log is
>
> COMMENT
> COMMENT
> COMMENT
> NOTICE: schema "public" already exists, skipping
> CREATE SCHEMA
> SET
> CREATE FUNCTION
> CREATE EVENT TRIGGER
>
> and my /usr/pkg/pgsql/errlog
>
> 2021-12-04 20:31:27.734 EST [14650] STATEMENT: select
> ST_3DMakeBox('POINT(0 0)', 'SRID=3;POINT(1 1)');
> 2021-12-04 20:31:28.293 EST [21988] WARNING: stats for "t.g" do not
exist
> 2021-12-04 20:31:28.294 EST [21988] WARNING: stats for "t.g" do not
exist
> 2021-12-04 20:31:28.295 EST [21988] WARNING: stats for "t.g" do not
exist
> 2021-12-04 20:31:28.304 EST [21988] WARNING: stats for "c1.g" do not
exist
> 2021-12-04 20:31:28.304 EST [21988] WARNING: stats for "c2.g" do not
exist
> 2021-12-04 20:31:28.304 EST [21988] WARNING: stats for "p.g" do not
exist
> 2021-12-04 20:31:28.306 EST [21988] WARNING: stats for "c2.g" do not
exist
> 2021-12-04 20:31:28.313 EST [21988] WARNING: stats for "p.g" do not
exist
> 2021-12-04 20:31:28.313 EST [21988] WARNING: stats for "p.g" do not
exist
> 2021-12-04 20:31:28.313 EST [21988] WARNING: stats for "c1.g" do not
exist
> 2021-12-04 20:31:28.313 EST [21988] WARNING: stats for "c1.g" do not
exist
> 2021-12-04 20:31:28.315 EST [21988] WARNING: stats for "p.g" do not
exist
> 2021-12-04 20:31:28.534 EST [15485] ERROR: mixed geometry type is not
> supported
> 2021-12-04 20:31:28.534 EST [15485] STATEMENT: select 'PL1', id,
> ST_AsText(geom) from ST_FromFlatGeobuf(null::flatgeobuf_t1, (
> select ST_AsFlatGeobuf(q) from (values
> ('POINT (1 2)'::geometry),
> ('POINT (3 4)'::geometry),
> ('POLYGON ((35 10, 45 45, 15 40, 10 20, 35 10), (20 30,
35 35, 30 20,
> 20 30))'::geometry)
> ) q)
> );
> 2021-12-04 20:31:28.833 EST [1047] LOG: server process (PID 16190) was
> terminated by signal 6: Abort trap
> 2021-12-04 20:31:28.833 EST [1047] DETAIL: Failed process was running:
> SELECT c, abs(ST_Distance(ply::geography, pt::geography) -
> _ST_DistanceUnCached(ply::geography, pt::geography)) < 0.01 FROM
> ( VALUES
> ('geog_distance_cached_1a', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1b', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1c', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1e', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1f', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1g', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)'),
> ('geog_distance_cached_1h', 'POLYGON((0 0, 0 10, 10 10, 10 0, 0
0))',
> 'POINT(5 5)')
> ) AS u(c,ply,pt);
> 2021-12-04 20:31:28.833 EST [1047] LOG: terminating any other active
> server processes
> 2021-12-04 20:31:28.833 EST [8837] WARNING: terminating connection
> because of crash of another server process
> 2021-12-04 20:31:28.833 EST [8837] DETAIL: The postmaster has
> commanded this server process to roll back the current transaction and
exit,
> because another server process exited abnormally and possibly corrupted
> shared memory.
> 2021-12-04 20:31:28.833 EST [8837] HINT: In a moment you should be able
> to reconnect to the database and repeat your command.
> 2021-12-04 20:31:28.842 EST [98] WARNING: terminating connection
> because of crash of another server process
> 2021-12-04 20:31:28.842 EST [98] DETAIL: The postmaster has commanded
> this server process to roll back the current transaction and exit, because
another
> server process exited abnormally and possibly corrupted shared memory.
> 2021-12-04 20:31:28.842 EST [98] HINT: In a moment you should be able
to
> reconnect to the database and repeat your command.
> 2021-12-04 20:31:28.852 EST [1047] LOG: all server processes
terminated;
> reinitializing
> 2021-12-04 20:31:29.116 EST [5701] LOG: database system was
interrupted;
> last known up at 2021-12-04 20:31:23 EST
> 2021-12-04 20:31:29.293 EST [5701] LOG: database system was not
properly
> shut down; automatic recovery in progress
> 2021-12-04 20:31:29.294 EST [5701] LOG: redo starts at 0/8E5349C0
> 2021-12-04 20:31:29.485 EST [5701] LOG: invalid record length at
> 0/8F1323E0: wanted 24, got 0
> 2021-12-04 20:31:29.485 EST [5701] LOG: redo done at 0/8F131F48
> 2021-12-04 20:31:29.485 EST [5701] LOG: last completed transaction was
at
> log time 2021-12-04 20:31:28.541784-05
> 2021-12-04 20:31:29.549 EST [1047] LOG: database system is ready to
accept
> connections
More information about the postgis-devel
mailing list