-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PGUpgrade failing #3999
Comments
for some additional info database with postgresql13 was initialized on host without hugepages, now it is running on host with hugepages enabled.
|
even running clean cluster on host without hugepages and trying pgupgrade on it also running pgupgrade on non hugapes host. It just fail. Same log as above. |
i was able to perform uprade using crunchy-upgrade:ubi8-5.5.0-0 So I think it is still something that should be addressed. Also these bus errors when running upgrade on host with hugepages. |
Please ensure you do the following when reporting a bug:
Note that some logs needed to troubleshoot may be found in the
/pgdata/<CLUSTERNAME>/pg_log
directory on your Postgres instance.An incomplete bug report can lead to delays in resolving the issue or the closing of a ticket, so please be as detailed as possible.
If you are looking for general support, please view the support page for where you can ask questions.
Thanks for reporting the issue, we're looking forward to helping you!
Overview
Pgupgrade fail when upgrading from postgres 13 to 16.
Images used:
crunchy-postgres:ubi8-13.8-1
crunchy-postgres:ubi8-16.3-1
Environment
Please provide the following details:
Kubernetes
,OpenShift
,Rancher
,GKE
,EKS
,AKS
etc.) Kubernetes1.20.3
,4.7.0
) v1.25.16ubi8-5.x.y-0
) ubi8-5.6.0-015
) 13 -> 16hostpath
,nfs
, or the name of your storage class) nfsSteps to Reproduce
New postgres 16 cannot be started log:
When running with PG13 image it also refuses now to start, but was healthy before upgrade:
REPRO
above
EXPECTED
pgupgrade complete without issues
ACTUAL
pgupgrade failed, and postgres cluster not starting at all with new version and with the old one.
Logs
Above
Additional Information
na
The text was updated successfully, but these errors were encountered: