You mean PG_13_202007201 was created by PG 13 ? No, there isn't any other clusters, maybe it was created by my previous failed attempts of upgrading.
So it seems it should be ok that I issue a command like this
find . -name "PG_13*"|xargs rm -rf
and then do upgrade again?
There should be a subdirectory under your tablespace directory for every
major version, e.g., PG_13_202007201. I have no idea why your _new_
version already has a directory there. Do you have a second cluster on
the machine that is using that tablespace directory for PG 13?
--
Bruce Momjian <bruce@xxxxxxxxxx> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
major version, e.g., PG_13_202007201. I have no idea why your _new_
version already has a directory there. Do you have a second cluster on
the machine that is using that tablespace directory for PG 13?
--
Bruce Momjian <bruce@xxxxxxxxxx> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
