Add more information about the incremental mode in documentation.

diff --git a/README b/README
index 0d0a60e73caadf0edbac6528ab76fd87dbd01d15..60520504fd60459ba4e4ecfb4ebaf93ce6214124 100644 (file)
--- a/README
+++ b/README
@@ -412,6 +412,12 @@ INCREMENTAL REPORTS
 
     you will have all daily and weekly reports for the full running period.
 
+    In this mode pgBagder will create an automatic incremental file into the
+    output directory, so you don't have to use the -l option unless you want
+    to change the path of that file. This mean that you can run pgBadger in
+    this mode each days on a log file rotated each week, it will not count
+    the log entries twice.
+
 BINARY FORMAT
     Using the binary format it is possible to create custom incremental and
     cumulative reports. For example, if you want to refresh a pgbadger

diff --git a/doc/pgBadger.pod b/doc/pgBadger.pod
index 1214c525711104ed6ec087638ec3bdca5e9025bb..b7766ea6d79aa84c349eff316c1b385a36fcc945 100644 (file)
--- a/doc/pgBadger.pod
+++ b/doc/pgBadger.pod
@@ -387,6 +387,12 @@ For example, if you run pgBadger as follow based on a daily rotated file:
 
 you will have all daily and weekly reports for the full running period.
 
+In this mode pgBagder will create an automatic incremental file into the
+output directory, so you don't have to use the -l option unless you want
+to change the path of that file. This mean that you can run pgBadger in
+this mode each days on a log file rotated each week, it will not count
+the log entries twice.
+
 =head1 BINARY FORMAT
 
 Using the binary format it is possible to create custom incremental and