The biggest thing that piqued my interest yesterday at pgCon was the lightning talk on pgbadger. I'm certainly going to take a look at this as a substitute for pgfouine, which I have sadly found largely unusable in most cases where I want it.
Interesting enough there has been a much better alternative to pgFouine for years -- mk-query-digest from Maatkit, now pt-query-digest from Percona Toolkit. But it never became widely used, perhaps because it was too closely associated with MySQL. The PostgreSQL log-parser is still part of pt-query-digest but because this isn't widely used, at some point I plan to remove that code to simplify maintenance and testing.
Hi Everybody,<br />
pgbadger is really nice, but here we are facing an issue or might be we are missing something that pgbadger report works fins but in report it doesn't shows any statement or graph even a full page get created.<br />
Statement used:<br />
./pgbadger -p -g -l /tmp/postgresql-2012-07-08_000000.log -f stderr -o /home/enterprisedb/pgbadger_graph_08-Jul.html<br />
I’ve been using Pgbadger1.2 on EDB9 the issue is that sometimes the log is parsed ie the time taken to parse the log is shown in the report but its an empty report.. Is that a bug with the version .<br />
Also i was looking at using zcat for .tgz log files but its not parsing the logs instead getting the following error:<br />
FATAL: unable to detect log file format from /pg_log/edb-2012-11-15.tgz, please use -f option.<br />
even after using -f the issue still remains ..<br />