Financial Advisor at a financial services firm with 10,001+ employees
Real User
Top 5
2025-03-27T15:58:43Z
Mar 27, 2025
While the flexibility of the server for financial reasons is understandable, better switching between primary and backup would make transitions smoother. I noticed an issue where the primary refuses to launch if the backup isn't running. Another improvement could be the ability to scale storage back down after scaling up, as we can do with compute resources. It's likely a financial restriction from Microsoft.
Support can certainly get better. I have had mixed experiences a lot of times. About 18 months ago, I had a fairly troublesome time with support. After raising multiple escalations, I think it has gotten a little better.
Director, Alliances & Engineering at a computer software company with 1,001-5,000 employees
MSP
Top 10
2024-11-21T16:37:00Z
Nov 21, 2024
Performance is one area that has constraints for our customers. I believe there could be improvements in the mirroring part and Change Data Capture (CDC).
Admin (hands on user) at a comms service provider with 11-50 employees
Real User
Top 20
2024-11-21T15:02:00Z
Nov 21, 2024
There aren't any notable areas for improvement that I could see. PostgreSQL was self-sufficient with no need for additional database knowledge to maintain it.
Technical Lead at SVA System Vertrieb Alexander GmbH
Real User
Top 10
2024-11-20T23:16:00Z
Nov 20, 2024
Perhaps a minor improvement could be made in simplifying user additions, allowing for an easier process rather than scripting it out. However, scripting is not a significant issue.
Product manager at a financial services firm with 5,001-10,000 employees
Real User
Top 20
2024-11-20T21:57:00Z
Nov 20, 2024
They can offer more RAG extensions. Currently, it only has the vector search. It does not presently support knowledge graph functionalities as Neo4j does. It also does not offer some tools to improve indexing the way other vector databases offer.
Learn what your peers think about Azure Database for PostgreSQL. Get advice and tips from experienced pros sharing their opinions. Updated: September 2025.
Azure Database for PostgreSQL can be improved by allowing quicker scaling without blips. It would help if it were more dynamic and required less planning. You can't just scale back performance and storage as needed. Adding flexible scaling capabilities would enhance performance, making it greener and more efficient. Additionally, addressing the reliability issue where the database might crash during sudden performance peaks would be beneficial. Azure PostgreSQL's monitoring and management tools are constantly improving, but costs can be challenging. Azure Monitor provides the default metrics, but if you want all the metrics, you need to enable all logging, which will have more cloud costs than the database itself.
Azure Database for PostgreSQL offers efficient management, robust networking, and seamless Microsoft integration. Known for its strong performance and high satisfaction in enterprise settings, it provides operational efficiency, security, and monitoring.With features that facilitate Azure integration, easy configuration, and AI integration, Azure Database for PostgreSQL serves as a valuable choice for businesses requiring operational efficiency and cost-effectiveness. Users benefit from...
While the flexibility of the server for financial reasons is understandable, better switching between primary and backup would make transitions smoother. I noticed an issue where the primary refuses to launch if the backup isn't running. Another improvement could be the ability to scale storage back down after scaling up, as we can do with compute resources. It's likely a financial restriction from Microsoft.
Support can certainly get better. I have had mixed experiences a lot of times. About 18 months ago, I had a fairly troublesome time with support. After raising multiple escalations, I think it has gotten a little better.
Performance is one area that has constraints for our customers. I believe there could be improvements in the mirroring part and Change Data Capture (CDC).
There aren't any notable areas for improvement that I could see. PostgreSQL was self-sufficient with no need for additional database knowledge to maintain it.
Perhaps a minor improvement could be made in simplifying user additions, allowing for an easier process rather than scripting it out. However, scripting is not a significant issue.
They can offer more RAG extensions. Currently, it only has the vector search. It does not presently support knowledge graph functionalities as Neo4j does. It also does not offer some tools to improve indexing the way other vector databases offer.
Azure Database for PostgreSQL can be improved by allowing quicker scaling without blips. It would help if it were more dynamic and required less planning. You can't just scale back performance and storage as needed. Adding flexible scaling capabilities would enhance performance, making it greener and more efficient. Additionally, addressing the reliability issue where the database might crash during sudden performance peaks would be beneficial. Azure PostgreSQL's monitoring and management tools are constantly improving, but costs can be challenging. Azure Monitor provides the default metrics, but if you want all the metrics, you need to enable all logging, which will have more cloud costs than the database itself.