This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 32%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
After performing multiple database restores on the Azure PostgreSQL Flexible Server Its was failing due to SSL connection. sql-mediohflow-beta-hyp-eastus-pg02, the server is now stuck in read-only mode.
SHOW default_transaction_read_only; returns on
current_setting('default_transaction_read_only') = on
source = configuration file
pg_is_in_recovery() = false
Restarting the server does NOT resolve the issue
An Azure managed PostgreSQL database service for app development and deployment.
I think… when FlexSrv keeps u read‑only like that, it’s the fabric not re‑binding the write‑volume after the failed restores, so the gentle fix is just making a new server from the same restore‑point in Portal and switching over.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 24%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Rayyan Mohammad
Thank you for the update and for confirming the storage threshold trigger. Based on the details shared, the behavior occurred because the server storage utilization reached a critical level while storage autogrow was disabled. When disk usage approaches the allocated limit, Azure Database for PostgreSQL Flexible Server can temporarily enforce a protective read-only state to prevent potential data corruption and maintain service stability. This is why the server reported default_transaction_read_only = on even though pg_is_in_recovery() returned false and restarts did not change the state.
After increasing the allocated storage from the Azure Portal under Compute + storage, the server exited the protective mode and normal read-write operations resumed, which can be validated by confirming that SHOW default_transaction_read_only; now returns off. To help prevent recurrence, it is recommended to enable Storage autogrow so the service can automatically expand storage when utilization approaches capacity, and to configure Azure Monitor alerts to notify you when storage usage reaches higher thresholds such as 80% or 90%. Regular monitoring of storage metrics will also help ensure sufficient capacity during periods of high ingestion or growth.
At this stage the server is operating normally. If you notice the read-only state returning after storage expansion, please share recent storage metrics and activity details so we can investigate further.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 95%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Hi Rayyan Mohammad
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
In our investigation, we have noticed that the server is in dropped state. I request you to please check and let me know if you have dropped the server from your end.