On Sat, Feb 23, 2013 at 12:55:07AM -0500, Charles Sprickman wrote:
>[...]
>The one huge downside to this is that the logs are so noisy, it's
>hard to track down errors and stats real-time since the query logging
>is so noisy.
> [...]
>Right now I'm considering just switching to syslog-ng or rsyslog
>and seeing if there's a way I can parse the non-query messages
>out and dump them in another logfile… Any pointers on that?
I use SEC for log analysis and I identify query logs by looking for
the duration entry in the first line. Then pull the triplet of:
hostname, pid and log line id (the 5 in [5-2], [5-3] etc.)
and find all the rest of the lines by matching that triplet.
>Without breaking compatibility with pgbadger, what
>log_line_prefix might make it easier to pick out
>statements (even when they span multiple lines)?
Just for reference I use:
'%t %u@%d(%p): '
--
-- rouilj
John Rouillard System Administrator
Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111
