Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 4177563267D for ; Mon, 1 Mar 2010 11:31:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 58642-04 for ; Mon, 1 Mar 2010 15:31:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211]) by mail.postgresql.org (Postfix) with ESMTP id 398A4632416 for ; Mon, 1 Mar 2010 11:31:19 -0400 (AST) Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.14.2/8.14.2) with ESMTP id o21FVGn3004575 for ; Mon, 1 Mar 2010 17:31:16 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) Received: from localhost (localhost [[UNIX: localhost]]) by smadev.internal.net (8.14.2/8.14.2/Submit) id o21FVFLW004574 for pgsql-admin@postgresql.org; Mon, 1 Mar 2010 17:31:15 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-admin@postgresql.org Subject: severely wierd problem & PgSQL log analyzer Date: Mon, 1 Mar 2010 17:31:15 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201003011731.15724.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.177 tagged_above=-10 required=5 tests=AWL=-0.992, BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201003/3 X-Sequence-Number: 33802 Hi, i am facing a very wierd situation, a piece of java code seems correct, however *some* times a connection instead of being rollbacked gets commited. (which has driven me nuts). So what i did, is replicate the problem with full logging enabled from java, in order to know at any point in the code against which postgres pid backend i am running against. At the same time i had full logging enabled in postgresql 8.3 and i tried to trace the exact backend which resulted in commit. (i try to replicate the problem by hitting the reload button in firefox). However that gives me about over 160 instances of the program, making difficult to put together all those sessions from the logs, and it seems i cannot see whats happening unless i have a handy tool that can extract info from the logs and present it in a human way. Any suggestions for a good pgsql log analyzer? i am currently struggling with http://pgfouine.projects.postgresql.org/tutorial.html (having failed with http://bucardo.org/wiki/Pgsi which wants only syslog) -- Achilleas Mantzios