From: Darold Gilles Date: Mon, 20 Jan 2014 08:34:53 +0000 (+0100) Subject: Add more information about the incremental mode in documentation. X-Git-Tag: v5.0~18 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5bb62ac7f852f3cd5a030e866c057ca7fb129a82;p=pgbadger Add more information about the incremental mode in documentation. --- diff --git a/README b/README index 0d0a60e..6052050 100644 --- 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 1214c52..b7766ea 100644 --- 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