<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Yah it is still an issue. I’ve just reopened that ticket. It was on me to provide a debug trace with SFCGAL symbols on windows so SFCGAL group could trace it. Seems the issue has only happened on windows so far so might be windows specific.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I confirmed the test Paul provided on that ticket<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Still crashes on windows – <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>PostgreSQL 13.1, compiled by Visual C++ build 1914, 64-bit<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>POSTGIS="3.1.0dev 3.1.0alpha2-157-gdfeaaac70" [EXTENSION] PGSQL="130" GEOS="3.9.0beta2-CAPI-0.15.1" SFCGAL="1.3.8" PROJ="6.3.2" GDAL="GDAL 3.2.0, released 2020/10/26" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.5.0 (Internal)" TOPOLOGY RASTER<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> postgis-users [mailto:postgis-users-bounces@lists.osgeo.org] <b>On Behalf Of </b>Mike Treglia<br><b>Sent:</b> Tuesday, December 8, 2020 9:48 PM<br><b>To:</b> PostGIS Users Discussion <postgis-users@lists.osgeo.org><br><b>Subject:</b> [postgis-users] Postgres Crash with st_orientation on single dataset<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi All,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I was just trying to troubleshoot something with a dataset, and when running st_orientation on it, postgres crashes. Potentially related to this old bug report? <a href="https://trac.osgeo.org/postgis/ticket/3651">https://trac.osgeo.org/postgis/ticket/3651</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'm working on Windows 10, 64 bit, with Postgres 13.0, with postgres and postgis installed through EnterpriseDB. PostGIS and related info is here:<o:p></o:p></p></div><div><p class=MsoNormal>POSTGIS="3.0.2 3.0.2" [EXTENSION] PGSQL="130" GEOS="3.8.1-CAPI-1.13.3" SFCGAL="1.3.8" PROJ="6.3.2" GDAL="GDAL 3.0.4, released 2020/01/28 GDAL_DATA not found" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)" TOPOLOGY RASTER<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Below is the log, which includes the sql statement (I renamed the dataset for some data anonymity in case that matters). I'm not sure if it's something about a specific feature, or the dataset itself that's causing an issue. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Mostly just wanted to share in case it's not a known issue, and if there's anything else I can provide that would be useful, happy to do so (though the dataset is not shareable, unfortunately).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Mike<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2020-12-08 21:32:16.998 EST [7136] LOG: server process (PID 24536) was terminated by exception 0xC00000FD<br>2020-12-08 21:32:16.998 EST [7136] DETAIL: Failed process was running: select st_orientation((st_dump(geom_2263)).geom) as orient, count(*) from nac_data.test_data <br><br>group by orient<br>2020-12-08 21:32:16.998 EST [7136] HINT: See C include file "ntstatus.h" for a description of the hexadecimal value.<br>2020-12-08 21:32:17.000 EST [7136] LOG: terminating any other active server processes<br>2020-12-08 21:32:17.022 EST [12112] WARNING: terminating connection because of crash of another server process<br>2020-12-08 21:32:17.022 EST [12112] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.<br>2020-12-08 21:32:17.022 EST [12112] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br>2020-12-08 21:32:17.022 EST [12008] WARNING: terminating connection because of crash of another server process<br>2020-12-08 21:32:17.022 EST [12008] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.<br>2020-12-08 21:32:17.022 EST [12008] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br>2020-12-08 21:32:17.034 EST [22696] WARNING: terminating connection because of crash of another server process<br>2020-12-08 21:32:17.034 EST [22696] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.<br>2020-12-08 21:32:17.034 EST [22696] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br>2020-12-08 21:32:17.033 EST [8476] WARNING: terminating connection because of crash of another server process<br>2020-12-08 21:32:17.033 EST [8476] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.<br>2020-12-08 21:32:17.033 EST [8476] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br>2020-12-08 21:32:17.033 EST [8476] CONTEXT: while scanning block 102119 of relation "results_scratch.nac_ecml2"<br>2020-12-08 21:32:17.036 EST [25352] WARNING: terminating connection because of crash of another server process<br>2020-12-08 21:32:17.036 EST [25352] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.<br>2020-12-08 21:32:17.036 EST [25352] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br>2020-12-08 21:32:17.060 EST [7136] LOG: all server processes terminated; reinitializing<br>2020-12-08 21:32:17.141 EST [23844] LOG: database system was interrupted; last known up at 2020-12-08 21:27:47 EST<br>2020-12-08 21:32:17.195 EST [22960] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.339 EST [25660] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.406 EST [26996] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.533 EST [3096] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.621 EST [26160] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.717 EST [23828] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.747 EST [23904] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.780 EST [24808] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.846 EST [26036] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.906 EST [1116] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:17.976 EST [22556] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:18.045 EST [28448] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:18.107 EST [25316] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:18.174 EST [22180] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:18.238 EST [14504] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:18.870 EST [13132] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:19.802 EST [24976] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:20.826 EST [28144] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:21.857 EST [18416] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:21.959 EST [23844] LOG: database system was not properly shut down; automatic recovery in progress<br>2020-12-08 21:32:21.971 EST [23844] LOG: redo starts at 7/E540C568<br>2020-12-08 21:32:22.834 EST [22308] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:23.892 EST [22736] FATAL: the database system is in recovery mode<br>2020-12-08 21:32:24.872 EST [27520] FATAL: the database system is in recovery mode<o:p></o:p></p></div></div></div></div></body></html>