Skip to content

Commit 7166c7f

Browse files
Added Azure Advisor Recommendations
1 parent e8aac4c commit 7166c7f

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

articles/postgresql/flexible-server/how-to-autovacuum-tuning.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -316,6 +316,17 @@ Autovacuum runs on tables with an insert-only workload. Two new server paramet
316316

317317
Using the feature troubleshooting guides that is available on the Azure Database for PostgreSQL flexible server portal it's possible to monitor bloat at database or individual schema level along with identifying potential blockers to autovacuum process. Two troubleshooting guides are available first one is autovacuum monitoring that can be used to monitor bloat at database or individual schema level. The second troubleshooting guide is autovacuum blockers and wraparound, which helps to identify potential autovacuum blockers. It also provides information on how far the databases on the server are from wraparound or emergency situation. The troubleshooting guides also share recommendations to mitigate potential issues. How to set up the troubleshooting guides to use them follow [setup troubleshooting guides](how-to-troubleshooting-guides.md).
318318

319+
320+
## Azure Advisor Recommendations
321+
322+
Azure Advisor recommendations are a proactive way of identifying if a server has a high bloat ratio or the server is approaching transaction wraparound scenario. You can also set alerts for the recommendations using the [Create Azure Advisor alerts on new recommendations using the Azure portal](<https://learn.microsoft.com/azure/advisor/advisor-alerts-portal>)
323+
324+
The recommendations are:
325+
326+
- **High Bloat Ratio**: High bloat ratio can impact server performance in multiple ways. One of these is the PG Engine Optimizer being unable to pick the best route which in turn leads to query performance degradation.
327+
328+
- **Transaction Wrap around**: This is one of the most serious issues a server can encounter. Once your server is in this state it might stop accepting any more transactions, causing the server to become read-only.
329+
319330
## Related content
320331

321332
- [High CPU Utilization](how-to-high-cpu-utilization.md)

0 commit comments

Comments
 (0)