Skip to content

Commit 0b7d560

Browse files
committed
updates
1 parent afda0f2 commit 0b7d560

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/postgresql/flexible-server/concepts-compare-single-server-flexible-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ The following table provides a list of high-level features and capabilities comp
113113
| Microsoft Defender for Cloud | Yes | No |
114114
| Resource health | Yes | Yes |
115115
| Service health | Yes | Yes |
116-
| Performance insights (iPerf) | Yes | Yes |
116+
| Performance insights (iPerf) | Yes | Yes. Not available in portal |
117117
| Major version upgrades support | No | No |
118118
| Minor version upgrades | Yes. Automatic during maintenance window | Yes. Automatic during maintenance window |
119119

articles/postgresql/single-server/how-to-optimize-query-stats-collection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article describes how to optimize query statistics collection on an Azure D
1717

1818
## Use pg_stats_statements
1919

20-
**Pg_stat_statements** is a PostgreSQL extension that's enabled by default in Azure Database for PostgreSQL. The extension provides a means to track execution statistics for all SQL statements executed by a server. This module hooks into every query execution and comes with a non-trivial performance cost. Enabling **pg_stat_statements** forces query text writes to files on disk.
20+
**Pg_stat_statements** is a PostgreSQL extension that can be enabled in Azure Database for PostgreSQL. The extension provides a means to track execution statistics for all SQL statements executed by a server. This module hooks into every query execution and comes with a non-trivial performance cost. Enabling **pg_stat_statements** forces query text writes to files on disk.
2121

2222
If you have unique queries with long query text or you don't actively monitor **pg_stat_statements**, disable **pg_stat_statements** for best performance. To do so, change the setting to `pg_stat_statements.track = NONE`.
2323

0 commit comments

Comments
 (0)