[postgis-users] Big Data issue

Shaozhong SHI shishaozhong at gmail.com
Thu Mar 17 19:39:07 PDT 2022


On Thursday, 17 March 2022, Marco Boeringa <marco at boeringa.demon.nl> wrote:

> Hi,
>
> Well, I guess it is not "best practice" to put a large number of
> geometries into a single row..., in whatever format you are using to do
> that.
>
> That said, I remember I once ran into an issue with either ST_Collect or
> ST_LineMerge, where PostgreSQL emitted an error about an array size
> exceeding some 32k values, and the processing stopped right there. So there
> may indeed be limitations to what PostgreSQL or PostGIS can realistically
> handle in specific rare cases.
>
> Marco
>
> Op 17-3-2022 om 14:34 schreef Shaozhong SHI:
>
>> I have a very large collection/array of geometries in on cell (one row
>> table).  Select * from table has never finished completion and got
>> terminated.
>>
>> A subsequent script uses ST_Concavehull, and got red marking when
>> running.  It never finished completion, but stopped.
>>
>> Can anyone enlighten me?
>>
>> Regards,
>>
>> David
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>



It uses 100 percent CPU but stops.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20220318/5ac83d27/attachment.html>


More information about the postgis-users mailing list