<div dir="ltr">Hello,<div><br></div><div>You followed the best practice to report it. Trac is officially a bug tracker.</div><div><br></div><div>Best way to get it fixed is to stomp it into a Github pull request with minimized version of your case in regress suite. </div><div>Somewhere in here: <a href="https://github.com/postgis/postgis/tree/master/raster/test/regress">https://github.com/postgis/postgis/tree/master/raster/test/regress</a> - press "Edit" on a file and post a branch with that issue.<br></div><div>After that, commit it as a pull request. CI (Travis) will run it and produce a non-optimized backtrace. It usually helps a tiny bit more, letting you understand what went wrong through all the "optimized out"-s.<br></div><div><br></div><div>Reasons why your report is hanging for now are: </div><div> - people have lives and postgis is a hobby;</div><div> - nobody really dug deep into raster codebase in last years, so you have a perfect opportunity to become world's best expert;</div><div> - it's synthetic query by a tool designed to break stuff, meaning there's no human being that wrote that query who you can empathize with to get thing fixed.</div><div><br></div><div>I've looked at your query and it looks like the whole report should have been just one line:<br><br><span style="font-family:monospace"><span style="color:rgb(0,0,0)">select st_union(null::raster, 4);<br></span></span><span style="font-family:monospace"><span style="color:rgb(0,0,0)">server closed the connection unexpectedly
</span><br> This probably means the server terminated abnormally
<br> before or while processing the request.<br>
<br></span></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 6, 2020 at 6:58 PM Jaime Casanova <<a href="mailto:jaime.casanova@2ndquadrant.com">jaime.casanova@2ndquadrant.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I reported a bug in postgis-devel[1] two days ago, and the day after<br>
that asked for a mantra for an osgeo id to report it in trac.<br>
<br>
None has received answers. So i wonder where is the best place to<br>
report these issues?<br>
i have another bug to report.<br>
<br>
[1] <a href="https://lists.osgeo.org/pipermail/postgis-devel/2020-June/028550.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/pipermail/postgis-devel/2020-June/028550.html</a><br>
-- <br>
Jaime Casanova <a href="http://www.2ndQuadrant.com" rel="noreferrer" target="_blank">www.2ndQuadrant.com</a><br>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services<br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div>Darafei Praliaskouski</div><div>Support me: <a href="http://patreon.com/komzpa" target="_blank">http://patreon.com/komzpa</a></div></div></div></div>