From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. 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 0077928..4b8a7de 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