From b4b8efbd3826ac0af2d1c2e7c40fcf80a4bfba45 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:03 +0200 Subject: Adding upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/progress-reporting.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/progress-reporting.html') diff --git a/doc/src/sgml/html/progress-reporting.html b/doc/src/sgml/html/progress-reporting.html index 7a88820..aeca080 100644 --- a/doc/src/sgml/html/progress-reporting.html +++ b/doc/src/sgml/html/progress-reporting.html @@ -1,5 +1,5 @@ -28.4. Progress Reporting
28.4. Progress Reporting
Prev UpChapter 28. Monitoring Database ActivityHome Next

28.4. Progress Reporting

28.4.1. ANALYZE Progress Reporting
28.4.2. CREATE INDEX Progress Reporting
28.4.3. VACUUM Progress Reporting
28.4.4. CLUSTER Progress Reporting
28.4.5. Base Backup Progress Reporting
28.4.6. COPY Progress Reporting

+28.4. Progress Reporting

28.4. Progress Reporting
Prev UpChapter 28. Monitoring Database ActivityHome Next

28.4. Progress Reporting

28.4.1. ANALYZE Progress Reporting
28.4.2. CREATE INDEX Progress Reporting
28.4.3. VACUUM Progress Reporting
28.4.4. CLUSTER Progress Reporting
28.4.5. Base Backup Progress Reporting
28.4.6. COPY Progress Reporting

PostgreSQL has the ability to report the progress of certain commands during command execution. Currently, the only commands which support progress reporting are ANALYZE, @@ -648,4 +648,4 @@

Number of tuples not processed because they were excluded by the WHERE clause of the COPY command. -


Prev Up Next
28.3. Viewing Locks Home 28.5. Dynamic Tracing
\ No newline at end of file +


Prev Up Next
28.3. Viewing Locks Home 28.5. Dynamic Tracing
\ No newline at end of file -- cgit v1.2.3