Date: Mon, 25 Feb 2013 14:59:38 +0000
From: John Rouillard <rouilj@renesys.com>
To: Charles Sprickman <spork@biglist.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: logging full queries separately
Message-ID: <20130225145938.GL7039@renesys.com>
References: <E2C417D4-A5C0-474C-8831-027A5E87C0A8@biglist.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <E2C417D4-A5C0-474C-8831-027A5E87C0A8@biglist.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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=E2=80=A6  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): '

--=20
				-- rouilj

John Rouillard       System Administrator
Renesys Corporation  603-244-9084 (cell)  603-643-9300 x 111


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin