<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 24, 2019, at 9:58 AM, <a href="mailto:rmrodriguez@carto.com" class="">rmrodriguez@carto.com</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">Already at 2.5.3…<br class="">postgis25_11-2.5.3-3.rhel7.x86_64<br class=""></blockquote><br class="">That's the binary, are the scripts installed in the database at 2.5.3 too?<br class=""></div></div></blockquote><div><br class=""></div><div>Yes, this isn’t a production system, this is a blank (with one spatial table) database created today just to test upgrading against packages.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">What would fixing 2.4 entail? Is there a ticket I can use to track this down? I think it’s worthwhile, probably.<br class=""></blockquote><br class="">It was done for 3 and 2.5 in <a href="https://trac.osgeo.org/postgis/ticket/4231" class="">https://trac.osgeo.org/postgis/ticket/4231</a><br class=""></div></div></blockquote><div><br class=""></div>Thanks,</div><div><br class=""></div><div>P</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><br class="">-- <br class="">Raúl Marín Rodríguez<br class=""><a href="http://carto.com" class="">carto.com</a><br class="">_______________________________________________<br class="">postgis-devel mailing list<br class="">postgis-devel@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</div></div></blockquote></div><br class=""></body></html>