Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id C98AC9FB303 for ; Tue, 26 Sep 2006 11:57:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 62539-05 for ; Tue, 26 Sep 2006 14:57:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6790B9FB29C for ; Tue, 26 Sep 2006 11:57:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8QEueg8025799; Tue, 26 Sep 2006 10:56:40 -0400 (EDT) To: Kyle Bateman cc: pgsql-sql@postgresql.org Subject: Re: Finding context for error log In-reply-to: <451936E9.1050201@actarg.com> References: <451936E9.1050201@actarg.com> Comments: In-reply-to Kyle Bateman message dated "Tue, 26 Sep 2006 08:19:21 -0600" Date: Tue, 26 Sep 2006 10:56:40 -0400 Message-ID: <25798.1159282600@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/166 X-Sequence-Number: 26377 Kyle Bateman writes: > Is there an easy way to get postgres to > spit out the SQL statement it was parsing when it generated the error? "log_min_error_statement = error" is what you're looking for. regards, tom lane