Hi Darafei,
Il giorno lun 25 gen 2021 alle ore 07:07 Darafei "Komяpa" Praliaskouski <
m...@komzpa.net> ha scritto:
> Yep, that's all pieces of multi-year cross-project improvement. We spent
> some years on algorithms, then we lacked infrastructure, now postgres added
> infrastructure and after th
my postgis verison details:
SELECT postgis_full_version();
POSTGIS="3.1.0 5e2af69" [EXTENSION] PGSQL="130" GEOS="3.9.0-CAPI-1.16.2"
PROJ="7.2.1" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0"
WAGYU="0.5.0 (Internal)" (core procs from "3.1.0alpha2 b6f415d" need
upgrade) TOPOLOGY (topology proc
postgis/postgis:latest image today. So I also could reproduce this error.
fyi.
POSTGIS="3.1.0 5e2af69" [EXTENSION] PGSQL="130" GEOS="3.7.1-CAPI-1.11.1
27a5e771" PROJ="Rel. 5.2.0, September 15th, 2018" LIBXML="2.9.4"
LIBJSON="0.12.1" LIBPROTOBUF="1.3.1" WAGYU="0.5.0 (Internal)" TOPOLOGY
man. 25. j
On Mon, Jan 25, 2021 at 10:19:42AM +0300, Fatih Sazan wrote:
> When I run my code running on PostGIS version 2.5, I don't get an error but
> when I run it on 3.1 it the server gives an error and enters the recovery
> mode every time.
> Operating System: CentOS Linux 8
> CPE OS Name: cpe:/o:centos:
