Thanks, Paul,
I'll be happy to share the data (will adjust a bit just to make it more
ambiguous re: what the data actually are). I think it'll be pretty large -
in DBeaver it's showing as 18GB for the table - I think generally just due
to complex geometries. Is there a preferred way to output
Hi Mike,
Nothing do you should ever cause a crash, so you've (a) found some data that
exercises the code in a new and exciting way, or (b) encountered a system
install issue, that is leading to a crash, and that's either (a) a bug or (b) a
system issue on your end (probably (a)). The first
Hi All,
I've attempted the following query that seems to be causing my database to
crash. Wondering if anyone is able to suggest anything actionable from the
postgis log, pasted below.
The query is fairly straightforward - trying to union/dissolve polygons
based on a few fields. But I know these
