logging full queries separately

From: Charles Sprickman <spork(at)biglist(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: logging full queries separately
Date: 2013-02-23 05:55:07
Message-ID: E2C417D4-A5C0-474C-8831-027A5E87C0A8@biglist.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message ktm@rice.edu 2013-02-23 16:35:28 Re: logging full queries separately
Previous Message domehead100 2013-02-22 22:11:03 base backup/restore + streaming replication => weirdness