[postgis-users] Database restarting while using ST Functions

[Daniel Baston]

Hi Pradeep,

The code fixes weren't ported back to the 2.1 branch. As a workaround,
maybe try replacing calls to ST_CollectionHomogenize(x) with
ST_CollectionHomogenize(ST_GeomFromEWKB(ST_AsEWKB(x))).

Dan


On Tue, Feb 6, 2018 at 7:08 AM, Pradeep Kanth G <pgundala at avineonindia.com>
wrote:

> Thanks Daniel,
>
>
>
> It is a PostGIS 2.1.9  (EDB 9.5),after upgrading to PostGIS 2.3(EDB 9.5)
> this issue has been resolved.
>
> However , we are testing EDB Development version 9.5.And there is no
> compatible with PostGIS 2.3 it will support only 2.1.9. So kindly let me
> know how to overcome this issue on 2.1.9.
>
>
>
>
>
> Regards
>
> Pradeep Kanth
>
>
>
> *From:* postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] *On
> Behalf Of *Daniel Baston
> *Sent:* Tuesday, February 6, 2018 5:13 PM
> *To:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Subject:* Re: [postgis-users] Database restarting while using ST
> Functions
>
>
>
> Hi Pradeep,
>
> Try checking the output of "SELECT postgis_full_version()". If you're not
> at the latest point-release, you should upgrade. There have been memory
> handling bugs with ST_CollectionHomogenize that could maybe cause the issue
> you're seeing.
>
> Dan
>
>
>
> On Tue, Feb 6, 2018 at 5:59 AM, Pradeep Kanth G <pgundala at avineonindia.com>
> wrote:
>
> Dear All,
>
>
>
> Kindly raise the below issue with EDB.
>
>
>
> *Observation* :  Database restarting while using  ST Functions.
>
> *Issue* :   Intersecting with two geometries, while using ST_Intersects
> and ST_CollectionHomogenize functions
>
> Database is restarting automatically.
>
> *Example*: ST_Intersects(ST_CollectionHomogenize(p.geometry,c.geometry))
>
> *Screenshot:*
>
>
>
>
>
> Regards
>
> Pradeep Kanth
>
>
>
>
>
> *Disclaimer *| The information contained in this electronic message
> (including any attachments) is intended for the exclusive use of the
> addressee(s) and may contain confidential or privileged information.If you
> have received this in error, please notify the sender immediately and
> delete the material from your machine. Any  action including review,
> retransmission, dissemination of this email or the attachments present
> along with the email by persons or entities other than the intended
> recipient is prohibited.
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
>
>
>
> *Disclaimer *| The information contained in this electronic message
> (including any attachments) is intended for the exclusive use of the
> addressee(s) and may contain confidential or privileged information.If you
> have received this in error, please notify the sender immediately and
> delete the material from your machine. Any  action including review,
> retransmission, dissemination of this email or the attachments present
> along with the email by persons or entities other than the intended
> recipient is prohibited.
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20180206/e6f75934/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17296 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20180206/e6f75934/attachment.png>