Date: Sat, 23 Feb 2013 10:35:28 -0600
From: "ktm@rice.edu" <ktm@rice.edu>
To: Charles Sprickman <spork@biglist.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: logging full queries separately
Message-ID: <20130223163528.GB19991@aart.rice.edu>
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-12-10)
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:
> Howdy,
>=20
> I've been finding that keeping full query logs is quite helpful; I starte=
d 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.
>=20
> Looking at the manual, I don't see any creative solutions to split the qu=
ery logs off from the rest of the logs.  Is there anything I've overlooked =
to take care of this?
>=20
> Right now I'm considering just switching to syslog-ng or rsyslog and seei=
ng 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?  Without breaking compatib=
ility with pgbadger, what log_line_prefix might make it easier to pick out =
statements (even when they span multiple lines)?
>=20
> Thanks,
>=20
> Charles
>=20

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


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