Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 66B996504D7 for ; Tue, 16 Dec 2008 21:19:52 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51657-02-5 for ; Tue, 16 Dec 2008 21:19:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by mail.postgresql.org (Postfix) with ESMTP id B3AFD6505DB for ; Tue, 16 Dec 2008 21:18:58 -0400 (AST) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id A5024AAD for ; Wed, 17 Dec 2008 02:18:55 +0100 (CET) Received: from saturn.localnet (saturn.i.zmi.at [10.0.0.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mailsrv.i.zmi.at (Postfix) with ESMTPSA id AC4CD2516 for ; Wed, 17 Dec 2008 02:18:55 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: slow slow query log Date: Wed, 17 Dec 2008 02:18:55 +0100 User-Agent: KMail/1.10.1 (Linux/2.6.27.8-ZMI; KDE/4.1.3; x86_64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1692200.uuR8IxIi1W"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200812170218.56155@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/119 X-Sequence-Number: 30952 --nextPart1692200.uuR8IxIi1W Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mittwoch 03 Dezember 2008 Vladimir Rusinov wrote: > Is there any way to disable dumping query parameters to query log? It > would be ok for us, if this would be just UPDATE table SET data=3D$1 > WHERE id=3D$2 on log, we don't need full text on log files. I'd like to have that info too. If you run a bayes database from=20 spamassassin, a single log entry can take 50+ lines. A restriction to=20 the number of lines, or length, would be very nice. mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart1692200.uuR8IxIi1W Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAklIU4AACgkQzhSR9xwSCbSLTgCdHBU+fcKSzhcUZW6iNiE/n0sV iPwAn01Lm2ttQdd/h5/SB8wgu2Vl0kNN =+/In -----END PGP SIGNATURE----- --nextPart1692200.uuR8IxIi1W--