From: Gilles Darold <gilles.darold@dalibo.com>
Date: Thu, 27 Dec 2018 22:40:06 +0000 (+0100)
Subject: Update pgbadger command examples.
X-Git-Tag: v10.2~2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d3a13a063fe96c5d070b5e71c11e9db51739b19a;p=pgbadger

Update pgbadger command examples.
---

diff --git a/README b/README
index 37f47ea..213faf4 100644
--- a/README
+++ b/README
@@ -191,22 +191,22 @@ SYNOPSIS
             # Log line prefix with syslog log output
             perl pgbadger --prefix 'user=%u,db=%d,client=%h,appname=%a' /pglog/postgresql-2012-08-21*
             # Use my 8 CPUs to parse my 10GB file faster, much faster
-            perl pgbadger -j 8 /pglog/postgresql-9.1-main.log
+            perl pgbadger -j 8 /pglog/postgresql-10.1-main.log
 
     Use URI notation for remote log file:
 
-            perl pgbadger http://172.12.19.1//var/log/postgresql/postgresql-9.1-main.log
-            perl pgbadger ftp://username.12.19.14/postgresql-9.1-main.log
-            perl pgbadger ssh://username.12.19.14//var/log/postgresql/postgresql-9.1-main.log.2.gz
+            perl pgbadger http://172.12.110.1//var/log/postgresql/postgresql-10.1-main.log
+            perl pgbadger ftp://username.12.110.14/postgresql-10.1-main.log
+            perl pgbadger ssh://username.12.110.14//var/log/postgresql/postgresql-10.1-main.log*
 
     You can use together a local PostgreSQL log and a remote pgbouncer log
     file to parse:
 
-            perl pgbadger /var/log/postgresql/postgresql-9.1-main.log ssh://username.12.19.14/pgbouncer.log
+            perl pgbadger /var/log/postgresql/postgresql-10.1-main.log ssh://username.12.110.14/pgbouncer.log
 
     Generate Tsung sessions XML file with select queries only:
 
-        perl pgbadger -S -o sessions.tsung --prefix '%t [%p]: user=%u,db=%d ' /pglog/postgresql-9.1.log
+        perl pgbadger -S -o sessions.tsung --prefix '%t [%p]: user=%u,db=%d ' /pglog/postgresql-10.1.log
 
     Reporting errors every week by cron job:
 
diff --git a/doc/pgBadger.pod b/doc/pgBadger.pod
index fb6e096..8a1476e 100644
--- a/doc/pgBadger.pod
+++ b/doc/pgBadger.pod
@@ -192,21 +192,21 @@ Examples:
 	# Log line prefix with syslog log output
 	perl pgbadger --prefix 'user=%u,db=%d,client=%h,appname=%a' /pglog/postgresql-2012-08-21*
 	# Use my 8 CPUs to parse my 10GB file faster, much faster
-	perl pgbadger -j 8 /pglog/postgresql-9.1-main.log
+	perl pgbadger -j 8 /pglog/postgresql-10.1-main.log
 
 Use URI notation for remote log file:
 
-	perl pgbadger http://172.12.19.1//var/log/postgresql/postgresql-9.1-main.log
-	perl pgbadger ftp://username.12.19.14/postgresql-9.1-main.log
-	perl pgbadger ssh://username.12.19.14//var/log/postgresql/postgresql-9.1-main.log.2.gz
+	perl pgbadger http://172.12.110.1//var/log/postgresql/postgresql-10.1-main.log
+	perl pgbadger ftp://username.12.110.14/postgresql-10.1-main.log
+	perl pgbadger ssh://username.12.110.14//var/log/postgresql/postgresql-10.1-main.log*
 
 You can use together a local PostgreSQL log and a remote pgbouncer log file to parse:
 
-	perl pgbadger /var/log/postgresql/postgresql-9.1-main.log ssh://username.12.19.14/pgbouncer.log
+	perl pgbadger /var/log/postgresql/postgresql-10.1-main.log ssh://username.12.110.14/pgbouncer.log
 
 Generate Tsung sessions XML file with select queries only:
 
-    perl pgbadger -S -o sessions.tsung --prefix '%t [%p]: user=%u,db=%d ' /pglog/postgresql-9.1.log
+    perl pgbadger -S -o sessions.tsung --prefix '%t [%p]: user=%u,db=%d ' /pglog/postgresql-10.1.log
 
 Reporting errors every week by cron job: