<?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 - yum</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, 29 Nov 2022 22:49:30 GMT</pubDate>

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

<item>
    <title>Using pg_upgrade to upgrade PostgreSQL 9.6 PostGIS 2.4 to PostgreSQL 15 3.3 on Yum</title>
    <link>https://www.bostongis.com/blog/index.php?/archives/278-Using-pg_upgrade-to-upgrade-PostgreSQL-9.6-PostGIS-2.4-to-PostgreSQL-15-3.3-on-Yum.html</link>
            <category>gis</category>
            <category>postgis postgresql</category>
            <category>yum</category>
    
    <comments>https://www.bostongis.com/blog/index.php?/archives/278-Using-pg_upgrade-to-upgrade-PostgreSQL-9.6-PostGIS-2.4-to-PostgreSQL-15-3.3-on-Yum.html#comments</comments>
    <wfw:comment>https://www.bostongis.com/blog/wfwcomment.php?cid=278</wfw:comment>

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

    <author>nospam@example.com (Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;PostgreSQL 15 came out just last week.  To celebrate the arrival of PostgreSQL 15, I will revisit the number one problem people have with PostGIS, how to upgrade your PostGIS enabled cluster, without installing an old PostGIS version.&lt;/p&gt;
&lt;p&gt;In a previous article &lt;a href=&quot;https://www.bostongis.com/blog/archives/268-pg_upgrade.html&quot;&gt;Using pg upgrade to upgrade PostGIS without installing older version&lt;/a&gt; I demonstrated a trick for upgrading to a newer PostgreSQL instance from PostGIS 2.2 - 2.whatever without having to install the older version of PostGIS in your new PostgreSQL service.
This is a revisit of that article, but with considerations for upgrading from a 2 series to a 3 series.&lt;/p&gt;

&lt;p&gt;Fear not.  Going from PostGIS 2+ to PostGIS 3+ can still be done without installing the old PostGIS 2+ in your new cluster.  Additionally once you are on PostGIS 3.1+, you should never have to do symlink or copy hacks to upgrade say PostGIS 3.1 to PostGIS 3.4. At least not for the same major version.&lt;/p&gt;

&lt;p&gt; If per chance you are on PostGIS 1 and trying to jump all the way to PostGIS 3+, then sadly you need to do a pg_dump of your old database/cluster and pg_restore into your new cluster.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;https://www.bostongis.com/blog/index.php?/archives/278-Using-pg_upgrade-to-upgrade-PostgreSQL-9.6-PostGIS-2.4-to-PostgreSQL-15-3.3-on-Yum.html#extended&quot;&gt;Continue reading &quot;Using pg_upgrade to upgrade PostgreSQL 9.6 PostGIS 2.4 to PostgreSQL 15 3.3 on Yum&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 16 Oct 2022 21:15:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.bostongis.com/blog/index.php?/archives/278-guid.html</guid>
    
</item>
<item>
    <title>Using pg_upgrade to upgrade PostgreSQL 9.3 PostGIS 2.1 to PostgreSQL 11 2.5 on Yum</title>
    <link>https://www.bostongis.com/blog/index.php?/archives/273-Using-pg_upgrade-to-upgrade-PostgreSQL-9.3-PostGIS-2.1-to-PostgreSQL-11-2.5-on-Yum.html</link>
            <category>gis</category>
            <category>postgis postgresql</category>
            <category>yum</category>
    
    <comments>https://www.bostongis.com/blog/index.php?/archives/273-Using-pg_upgrade-to-upgrade-PostgreSQL-9.3-PostGIS-2.1-to-PostgreSQL-11-2.5-on-Yum.html#comments</comments>
    <wfw:comment>https://www.bostongis.com/blog/wfwcomment.php?cid=273</wfw:comment>

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

    <author>nospam@example.com (Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;In a previous article &lt;a 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&quot;&gt;Using pg upgrade to upgrade PostGIS without installing older version&lt;/a&gt; I demonstrated a trick for upgrading to a newer PostgreSQL instance from PostGIS 2.2 - 2.whatever without having to install the older version of PostGIS in your new PostgreSQL service.
Unfortunately that trick does not work if coming from PostGIS 2.1 because in PostGIS 2.2 we renamed a c lib function that backed sql functions in 2.1.&lt;/p&gt;

&lt;p&gt;Fear not.  There is still a way to upgrade from 2.1 to 2.5 without installing an older version of PostGIS in your new PostgreSQL instance. To do so, you need to add a step and that is to remove the functions in 2.1 that are backed by this renamed lib function.  In upcoming PostGIS 3.0, we&#039;ve added this function back and have it throw an error so that even coming from PostGIS 2.1, you can upgrade just the same as you do from later versions.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;https://www.bostongis.com/blog/index.php?/archives/273-Using-pg_upgrade-to-upgrade-PostgreSQL-9.3-PostGIS-2.1-to-PostgreSQL-11-2.5-on-Yum.html#extended&quot;&gt;Continue reading &quot;Using pg_upgrade to upgrade PostgreSQL 9.3 PostGIS 2.1 to PostgreSQL 11 2.5 on Yum&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 01 Jan 2019 01:48:00 -0500</pubDate>
    <guid isPermaLink="false">https://www.bostongis.com/blog/index.php?/archives/273-guid.html</guid>
    
</item>

</channel>
</rss>
