Re: What to do with tablespaces when upgrading to pg13 from pg1X?

Got you, thanks a lot Bruce!
 
 
------------------ Original ------------------
From: &nbsp;"Bruce Momjian"<bruce(at)momjian(dot)us&gt;;
Date: &nbsp;Tue, Jan 12, 2021 11:01 AM
To: &nbsp;"James(王旭)"<wangxu(at)gu360(dot)com&gt;;
Cc: &nbsp;"pgsql-general"<pgsql-general(at)postgresql(dot)org&gt;;
Subject: &nbsp;Re: What to do with tablespaces when upgrading to pg13 from pg1X?

&nbsp;

On Tue, Jan 12, 2021 at 10:50:16AM +0800, James(王旭) wrote:
&gt; You mean PG_13_202007201 was created by PG 13 ? No, there isn't any other
&gt; clusters, maybe it was created by my previous failed attempts of upgrading.

Yes, it had to be created by PG 13 --- it starts with PG_13, followed by
the system catalog version.&nbsp; Yes, it might be left over.&nbsp; You have to
delete the old cluster and its tablespaces when you re-try.

&gt; So it seems it should be ok that I issue a command like this
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; find . -name "PG_13*"|xargs rm -rf
&gt;
&gt; and then do upgrade again?

I suggest you do more research than just run that --- at least I would.

--
&nbsp; Bruce Momjian&nbsp; <bruce(at)momjian(dot)us&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://momjian.us
&nbsp; EnterpriseDB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://enterprisedb.com

&nbsp; The usefulness of a cup is in its emptiness, Bruce Lee