Обсуждение: Unable to upgrade from 12.7 to 15.2
Hello All,
we are facing below issues while upgrading the cluster from 12.7 to 15.2.
The OLD cluster contains cstore_fdw extension and we have installed Citus(updated version of cstore_fdw) in postgresql 15.2 , we are not able to proceed further as the below error is the blocker for the same, any help regarding this will be much helpful.
TESTHOST:/tmp $ $NEW_PG_PATH/bin/pg_upgrade -b $OLD_PG_PATH/bin/ -B $NEW_PG_PATH/bin/ -d $OLD_PG_DATA -D $NEW_PG_DATA --check
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Checking for incompatible polymorphic functions ok
New cluster database "postgres" is not empty: found relation "columnar_internal.options"
Failure, exiting
Thanks,
Mahesh.
On Thu, Apr 20, 2023 at 6:14 AM Mahesh mana <maheshbabumms12@gmail.com> wrote:
Hello All,we are facing below issues while upgrading the cluster from 12.7 to 15.2.The OLD cluster contains cstore_fdw extension and we have installed Citus(updated version of cstore_fdw) in postgresql 15.2 , we are not able to proceed further as the below error is the blocker for the same, any help regarding this will be much helpful.TESTHOST:/tmp $ $NEW_PG_PATH/bin/pg_upgrade -b $OLD_PG_PATH/bin/ -B $NEW_PG_PATH/bin/ -d $OLD_PG_DATA -D $NEW_PG_DATA --checkPerforming Consistency Checks-----------------------------Checking cluster versions okChecking database user is the install user okChecking database connection settings okChecking for prepared transactions okChecking for system-defined composite types in user tables okChecking for reg* data types in user tables okChecking for contrib/isn with bigint-passing mismatch okChecking for user-defined encoding conversions okChecking for user-defined postfix operators okChecking for incompatible polymorphic functions okNew cluster database "postgres" is not empty: found relation "columnar_internal.options"Failure, exitingThanks,Mahesh.
I'd imagine you cannot have the extension pre-created in the new cluster before the upgrade proceeds. Especially if it's a newer version. You may have to do the upgrade with the old version of the extension installed and then update to the new version after the PG upgrade.
If you don't get any further responses on this list, it may be better to try and contact Citus for further support or make an issue on their github - https://github.com/citusdata/cstore_fdw/issues
Keith, you are absolutely correct. Mahesh transfer all the extensions from the old server to the new server before upgrading
On Thu, Apr 20, 2023 at 9:13 AM Keith Fiske <keith.fiske@crunchydata.com> wrote:
On Thu, Apr 20, 2023 at 6:14 AM Mahesh mana <maheshbabumms12@gmail.com> wrote:Hello All,we are facing below issues while upgrading the cluster from 12.7 to 15.2.The OLD cluster contains cstore_fdw extension and we have installed Citus(updated version of cstore_fdw) in postgresql 15.2 , we are not able to proceed further as the below error is the blocker for the same, any help regarding this will be much helpful.TESTHOST:/tmp $ $NEW_PG_PATH/bin/pg_upgrade -b $OLD_PG_PATH/bin/ -B $NEW_PG_PATH/bin/ -d $OLD_PG_DATA -D $NEW_PG_DATA --checkPerforming Consistency Checks-----------------------------Checking cluster versions okChecking database user is the install user okChecking database connection settings okChecking for prepared transactions okChecking for system-defined composite types in user tables okChecking for reg* data types in user tables okChecking for contrib/isn with bigint-passing mismatch okChecking for user-defined encoding conversions okChecking for user-defined postfix operators okChecking for incompatible polymorphic functions okNew cluster database "postgres" is not empty: found relation "columnar_internal.options"Failure, exitingThanks,Mahesh.I'd imagine you cannot have the extension pre-created in the new cluster before the upgrade proceeds. Especially if it's a newer version. You may have to do the upgrade with the old version of the extension installed and then update to the new version after the PG upgrade.If you don't get any further responses on this list, it may be better to try and contact Citus for further support or make an issue on their github - https://github.com/citusdata/cstore_fdw/issues--
On Thu, Apr 20, 2023 at 11:42:58AM -0400, Benjamin Acquaye wrote: > Keith, you are absolutely correct. Mahesh transfer all the extensions from the > old server to the new server before upgrading Yes, you have to _install_ the extensions in the new cluster at the operating system level only, nothing more. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.