postgresql database after major version upgrade is not available

Question

postgresql database after major version upgrade is not available

Tamás Rózsa 45

I have started a major version upgrade from pgSQL v14 to 16. In the first 2-3 hours the browser was open and the deployment was ongoing. After my notebook restart some hours later and re-enter the azure portal I cannot find the deployment activity progress any more, the database status is ready, but I cannot connect to the server, as the error message sais there is no pg_conf data.

Resourcegroup: VisibleFarm

Postgres SQL flexible database: visiblefarm-db

Saraswathi Devadula 4,765 Reputation points Microsoft External Staff Moderator

2025-05-26T00:23:30.3066667+00:00

Hello Tamás Rózsa

I kindly request you to please share the details requested in the private message for better troubleshooting.
Saraswathi Devadula 4,765 Reputation points Microsoft External Staff Moderator

2025-05-27T04:04:02.9633333+00:00

Hello Tamás Rózsa

We collaborated internally and successfully restored the server to its online state.

The team provided an update regarding the upgrade operation you initiated on May 25th. It was still in progress, which resulted in the 'server busy' error preventing further upgrades. They attempted to cancel the operation, and your server is now completely healthy.

However, they recommend avoiding major version upgrades until their analysis is complete, as they are working to prevent future issues.

Additionally, they are first testing the changes on the non-production server. If everything goes smoothly, they will apply the same updates to the production server.

The estimated timeframe to complete the analysis is five days.
Tamás Rózsa 45 Reputation points

2025-05-30T09:08:06.73+00:00

As we have discussed in private messages: I could not wait more for your solution. As we have discussed about the errors in the production environment, I have made a new resource deploy using a backup restore. I have made backups of the smaller databases and deleted them from the server, in the larger databases I have deleted all indexes and views and after it I have successfully made a major upgrade there. I am now making the restore, rebuilding the indexes and change our application to redirect to the new database. Now I still need to bring through the differential data was created in the backup replica in the last days. It is a lot of work :(, but at least now I have a pgSQL 16 with our data. So the technical part of this issue is closed with this workaround. If you have any explanation it would be interesting, but you do not need to push to correct the visiblefarm-db environment any more.

Please DO NOT invest 5 days to complete the analysis of the possible update of the visiblefarm-db server.

I do need only one more help: the temporarily database resources will cost us a significant additional cost. I would ask you to help me and redirect this issue to the azure invoicing center to be able to ask a discount for the resources which was made and used in the last days because of the errors of the azure environment.

Accepted answer

0 additional answers

Your answer

Saraswathi Devadula 4,765 Reputation points Microsoft External Staff Moderator

2025-05-26T00:23:30.3066667+00:00

Hello Tamás Rózsa

I kindly request you to please share the details requested in the private message for better troubleshooting.
Saraswathi Devadula 4,765 Reputation points Microsoft External Staff Moderator

2025-05-27T04:04:02.9633333+00:00

Hello Tamás Rózsa

We collaborated internally and successfully restored the server to its online state.

The team provided an update regarding the upgrade operation you initiated on May 25th. It was still in progress, which resulted in the 'server busy' error preventing further upgrades. They attempted to cancel the operation, and your server is now completely healthy.

However, they recommend avoiding major version upgrades until their analysis is complete, as they are working to prevent future issues.

Additionally, they are first testing the changes on the non-production server. If everything goes smoothly, they will apply the same updates to the production server.

The estimated timeframe to complete the analysis is five days.
Tamás Rózsa 45 Reputation points

2025-05-30T09:08:06.73+00:00

As we have discussed in private messages: I could not wait more for your solution. As we have discussed about the errors in the production environment, I have made a new resource deploy using a backup restore. I have made backups of the smaller databases and deleted them from the server, in the larger databases I have deleted all indexes and views and after it I have successfully made a major upgrade there. I am now making the restore, rebuilding the indexes and change our application to redirect to the new database. Now I still need to bring through the differential data was created in the backup replica in the last days. It is a lot of work :(, but at least now I have a pgSQL 16 with our data. So the technical part of this issue is closed with this workaround. If you have any explanation it would be interesting, but you do not need to push to correct the visiblefarm-db environment any more.

Please DO NOT invest 5 days to complete the analysis of the possible update of the visiblefarm-db server.

I do need only one more help: the temporarily database resources will cost us a significant additional cost. I would ask you to help me and redirect this issue to the azure invoicing center to be able to ask a discount for the resources which was made and used in the last days because of the errors of the azure environment.

Answer 1

PratikLad 1,585 Microsoft External Staff Moderator

Hello Tamás Rózsa

We have checked internally, and the update is, the server upgrade failed because the PostgreSQL (PG) container didn’t start properly. When we tried to roll back, that process got stuck because it wasn’t checking if the containers were actually healthy. One container was stuck, and another took longer than expected to start.

Now your servers are in healthy stare now you can try for major version upgrade now.

If still issue persist you can reach out to us.

I hope this has been helpful! Kindly consider upvoting the Answer if the information provided is helpful. This can assist other community members in resolving similar issues. Happy to help you.

PratikLad 1,585 Reputation points Microsoft External Staff Moderator

2025-06-04T08:35:52.4133333+00:00

Hello Tamás Rózsa,

We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

Please do let us know if you have any further queries.
PratikLad 1,585 Reputation points Microsoft External Staff Moderator

2025-06-05T10:10:04.29+00:00

Hello Tamás Rózsa,

We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

Please do let us know if you have any further queries.
Tamás Rózsa 45 Reputation points

2025-06-06T07:44:56.0266667+00:00

I have responded at 30th of May. We are using a new database server now.

The information that a container was unhealthy does not really help, as there is no information how would it be possible to check it prior an upgrade process. If there is any way, please share it with us. Thanks.

Share via

postgresql database after major version upgrade is not available

0 additional answers

Your answer