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.
pgadmin4 messages:(*"Connection to the server has been lost."*).
postgresql log : "*WARNING: terminating connection because of cr
>
> To add the support for different geometries, like polygons, you would need
> before to define some sorting algorithm similar to Z-order for points - not
> sure the same algos can be used for other geometries, maybe reducing them
> to the related bbox and considering the bbox vertices? Although
Hi Giuseppe,
You can order the inputs by anything you like; OVER(ORDER BY feature_id)
would work just as well. If you have an example that is not deterministic
despite ordered inputs, I'd be curious to see it if you can share.
Thanks,
Dan
On Sun, Jan 24, 2021 at 12:33 PM Giuseppe Broccolo
wrote
Hi Daniel,
Il giorno ven 22 gen 2021 alle ore 18:07 Daniel Baston
ha scritto:
> It should be deterministic for most real data if the inputs are ordered
> consistently, using the OVER() clause as you suggest. It's possible that
> there may be a contrived situation involving duplicates in the inpu
Hi Marco,
Il giorno sab 23 gen 2021 alle ore 11:39 Marco Boeringa <
ma...@boeringa.demon.nl> ha scritto:
> Hi Darafei,
>
> How does this relate to e.g. PostGIS with polygon or line data?
>
It doesn't. The patch Darafei shared in his reply added the possibility to
define a further support functio
