Skip to content

Commit 041fb06

Browse files
Merge pull request #276487 from nachoalonsoportillo/patch-1
Add note about limitation in servers with VNET Integration
2 parents b30420d + 185fb5e commit 041fb06

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/postgresql/flexible-server/concepts-index-tuning.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -184,6 +184,10 @@ When an Azure Database for PostgreSQL - Flexible Server instance is in read-only
184184

185185
Also, index tuning isn't supported currently on read replicas. Any recommendations seen on a read replica, is one that has been produced on the primary replica after having analyzed the workload recorded in it.
186186

187+
### Network connectivity method
188+
189+
Index tuning is currently supported on instances whose connectivity method is configured as [Public access (allowed IP addresses)](concepts-networking-public.md). For instances configured with [Private access (VNET Integration)](concepts-networking-private.md) the feature can be enabled, but it won't generate recommendations.
190+
187191
### Important considerations
188192

189193
If you have [high availability](../../reliability/reliability-postgresql-flexible-server.md) or [read replicas](concepts-read-replicas.md) configured on your server, be aware of the implications associated with producing write-intensive workloads on the primary server when recommended indexes are created by the index tuning feature. Be especially careful when creating indexes whose size is estimated to be large.

0 commit comments

Comments
 (0)