<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>BostonGIS -  waiting_postgis_25</title>
    <link>https://www.bostongis.com/blog/</link>
    <description>Open Source GIS</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.6.0 - http://www.s9y.org/</generator>
    <pubDate>Tue, 19 Jun 2018 07:59:16 GMT</pubDate>

    <image>
    <url>https://www.bostongis.com/blog/templates/default/img/s9y_banner_small.png</url>
    <title>RSS: BostonGIS -  waiting_postgis_25 - Open Source GIS</title>
    <link>https://www.bostongis.com/blog/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>Coming PostGIS 2.5 ST_OrientedEnvelope</title>
    <link>https://www.bostongis.com/blog/index.php?/archives/270-Coming-PostGIS-2.5-ST_OrientedEnvelope.html</link>
            <category> waiting_postgis_25</category>
            <category>postgis postgresql</category>
    
    <comments>https://www.bostongis.com/blog/index.php?/archives/270-Coming-PostGIS-2.5-ST_OrientedEnvelope.html#comments</comments>
    <wfw:comment>https://www.bostongis.com/blog/wfwcomment.php?cid=270</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://www.bostongis.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=270</wfw:commentRss>
    

    <author>nospam@example.com (Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;PostGIS 2.5 is just around the corner. One of the new functions coming is the &lt;a href=&quot;https://postgis.net/docs/manual-dev/ST_OrientedEnvelope.html&quot; target=&quot;_blank&quot;&gt;ST_OrientedEnvelop&lt;/a&gt;. This is something I&#039;ve been waiting for for years.
It is the true minimum bounding rectangle, as opposed to &lt;a href=&quot;https://postgis.net/docs/manual-dev/ST_Envelope.html&quot; target=&quot;_blank&quot;&gt;ST_Envelope&lt;/a&gt;  which is an axis aligned bounding rectable.&lt;/p&gt;

&lt;p&gt;Below is a pictorial view showing the difference between the two.&lt;/p&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;https://www.bostongis.com/blog/index.php?/archives/270-Coming-PostGIS-2.5-ST_OrientedEnvelope.html#extended&quot;&gt;Continue reading &quot;Coming PostGIS 2.5 ST_OrientedEnvelope&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 18 Jun 2018 17:42:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.bostongis.com/blog/index.php?/archives/270-guid.html</guid>
    
</item>
<item>
    <title>Using pg_upgrade to upgrade PostGIS without installing an older version of PostGIS</title>
    <link>https://www.bostongis.com/blog/index.php?/archives/268-Using-pg_upgrade-to-upgrade-PostGIS-without-installing-an-older-version-of-PostGIS.html</link>
            <category> waiting_postgis_25</category>
            <category>postgis postgresql</category>
    
    <comments>https://www.bostongis.com/blog/index.php?/archives/268-Using-pg_upgrade-to-upgrade-PostGIS-without-installing-an-older-version-of-PostGIS.html#comments</comments>
    <wfw:comment>https://www.bostongis.com/blog/wfwcomment.php?cid=268</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://www.bostongis.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=268</wfw:commentRss>
    

    <author>nospam@example.com (Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;PostGIS releases a new minor version of PostGIS every one or two years.  Each minor version of postgis has a different libname suffix.
In PostGIS 2.1 you&#039;ll find files in your PostgreSQL lib folder called postgis-2.1.*, rtpostgis-2.1.*, postgis-topology-2.1.*, address-standardizer-2.1.* etc.
and in a PostGIS 2.2 you&#039;ll find similar files but with 2.2 in the name.  I believe PostGIS and pgRouting are the only extensions that stamp the lib with a version number.  
Most other extensions you will find are just called extension.so e.g. hstore is always called hstore.dll /hstore.so even if the version changed from 9.6 to 10.
On the bright side this allows people to have two versions of PostGIS installed in a PostgreSQL cluster, though a database can use at most  one version.
So you can have an experimental database running a very new or unreleased version of PostGIS and a production database running a more battery tested version.&lt;/p&gt;

&lt;p&gt;On the sad side this causes a lot of PostGIS users frustration trying to use pg_upgrade to upgrade from an older version of PostGIS/PostgreSQL to a newer version of PostGIS/PostgreSQL;
as their pg_upgrade often bails with a message in the loaded_libraries.txt log file something to the affect:&lt;/p&gt;
&lt;pre&gt;could not load library &quot;$libdir/postgis-2.2&quot;: ERROR:  could not access file &quot;$libdir/postgis-2.2&quot;: No such file or directory
could not load library &quot;$libdir/postgis-2.3&quot;: ERROR:  could not access file &quot;$libdir/postgis-2.3&quot;: No such file or directory&lt;/pre&gt; &lt;/p&gt;

&lt;p&gt;This is also a hassle because we generally don&#039;t support a newer version of PostgreSQL on older PostGIS installs because the PostgreSQL major version changes tend to break our code
often and backporting those changes is both time-consuming and dangerous.  For example &lt;a href=&quot;https://trac.osgeo.org/postgis/ticket/3867&quot; target=&quot;_blank&quot;&gt;the DatumGetJsonb change&lt;/a&gt; 
and this &lt;a href=&quot;https://trac.osgeo.org/postgis/ticket/3904&quot;&gt;PostgreSQL 11 crasher&lt;/a&gt; we haven&#039;t isolated the cause of yet. There are several changes like this that have already made the PostGIS 2.4.0
we released recently incompatible with the PostgreSQL 11 head development.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;https://www.bostongis.com/blog/index.php?/archives/268-Using-pg_upgrade-to-upgrade-PostGIS-without-installing-an-older-version-of-PostGIS.html#extended&quot;&gt;Continue reading &quot;Using pg_upgrade to upgrade PostGIS without installing an older version of PostGIS&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 15 Oct 2017 01:11:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.bostongis.com/blog/index.php?/archives/268-guid.html</guid>
    
</item>

</channel>
</rss>
