From 323bcca5249c707b68d9f6d921d86fd750bcf33e Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 14 May 2024 21:16:20 +0200 Subject: Merging upstream version 16.3. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/indexes-examine.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/indexes-examine.html') diff --git a/doc/src/sgml/html/indexes-examine.html b/doc/src/sgml/html/indexes-examine.html index 29e43b1..cce0505 100644 --- a/doc/src/sgml/html/indexes-examine.html +++ b/doc/src/sgml/html/indexes-examine.html @@ -1,5 +1,5 @@ -11.12. Examining Index Usage
11.12. Examining Index Usage
Prev UpChapter 11. IndexesHome Next

11.12. Examining Index Usage #

+11.12. Examining Index Usage

11.12. Examining Index Usage
Prev UpChapter 11. IndexesHome Next

11.12. Examining Index Usage #

Although indexes in PostgreSQL do not need maintenance or tuning, it is still important to check which indexes are actually used by the real-life query workload. @@ -79,4 +79,4 @@ appropriate, then you might have to resort to forcing index usage explicitly. You might also want to contact the PostgreSQL developers to examine the issue. -

Prev Up Next
11.11. Indexes and Collations Home Chapter 12. Full Text Search
\ No newline at end of file +

Prev Up Next
11.11. Indexes and Collations Home Chapter 12. Full Text Search
\ No newline at end of file -- cgit v1.2.3