From: | Zaid Shabbir <zaidshabbir(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Cluster forcefully removal without user input |
Date: | 2024-05-31 02:48:16 |
Message-ID: | CABCJe_WYKbBXJtSvEea0Fs1hYTmgvZxJ7-V8h0QYG6Fihcye9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I have installed PostgreSQL 15 and PostgreSQL 14 side by side and want to
upgrade from 14 to 15. For upgrading purposes, I am using {postgresql-15-setup
check_upgrade}. However, in my case, the installed 14 version is not
compatible with the latest 15.7.
After the installation and cluster initialization of PostgreSQL 14 and 15,
when I run the following command {postgresql-15-setup check_upgrade}, it
returns the following message:
"Performing upgrade check: Upgrade failed. Removing the new cluster. Please
re-initdb the new cluster. failed "
After the failure the postgresql15 cluster removed forcefully due to the
following code written in postgresql-15-setup script file
{
if [ $script_result -eq 0 ]; then
echo $"OK"
else
# Clean up after failure
echo "Upgrade failed. Removing the new cluster. Please re-initdb
the new cluster."
* rm -rf "$PGDATA"* echo $"failed"
fi
}
My concern here is whether forcefully deleting the user cluster without
obtaining permission from the user is the right approach.
Regards,
Zaid Shabbir
AGEDB
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-05-31 03:25:58 | Re: Use generation memory context for tuplestore.c |
Previous Message | Kaiting Chen | 2024-05-31 02:06:51 | Explicit specification of index ensuring uniqueness of foreign columns |