Howdy,
I've been finding that keeping full query logs is quite helpful; I started doing this to be able to run pgbadger each
dayto get a nice overview of what's going on with the db servers. The one huge downside to this is that the logs are
sonoisy, it's hard to track down errors and stats real-time since the query logging is so noisy.
Looking at the manual, I don't see any creative solutions to split the query logs off from the rest of the logs. Is
thereanything I've overlooked to take care of this?
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
messagesout and dump them in another logfile… Any pointers on that? Without breaking compatibility with pgbadger,
whatlog_line_prefix might make it easier to pick out statements (even when they span multiple lines)?
Thanks,
Charles