On Sat, Feb 23, 2013 at 12:55:07AM -0500, Charles Sprickman wrote: > Howdy, > > I've been finding that keeping full query logs is quite helpful; I started doing this to be able to run pgbadger each day to get a nice overview of what's going on with the db servers. 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. > > Looking at the manual, I don't see any creative solutions to split the query logs off from the rest of the logs. Is there anything 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 messages out and dump them in another logfile… Any pointers on that? Without breaking compatibility with pgbadger, what log_line_prefix might make it easier to pick out statements (even when they span multiple lines)? > > Thanks, > > Charles > Hi Charles, Using syslog will work well for this. I would definitely recommend rsyslog over syslog-ng. We have a system running both and rsyslog is more efficient with less overhead and is less costly than syslog-ng for some functionality. Regards, Ken -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
