From: Richard Huxton <dev@archonet.com>
To: Lane Van Ingen <lvaningen@esncc.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: How to Log SELECT Statements Having Errors
Date: Tue, 15 Nov 2005 08:46:11 +0000
Message-ID: <4379A053.3010501@archonet.com> (raw)
In-Reply-To: <EKEMKEFLOMKDDLIALABIAEAICFAA.lvaningen@esncc.com>
References: <EKEMKEFLOMKDDLIALABIAEAICFAA.lvaningen@esncc.com>
Lane Van Ingen wrote:
> We are putting a new application on PostgreSQL 8.0.1 (Windows 2003);
> we are coming off of MySQL, and are having a hard time finding all of
> the offending SQL calls.
>
> It would help a great deal if I could log the content of any SQL calls
> that fail. Am only interested in SELECT statements.
I don't know that you can only log SELECT statements that cause errors.
It should be simple enough to log all statements that cause errors though:
log_min_messages = error
log_min_error_statement = error
> Noticed the following:
> (1) The PostgreSQL manual says that config parm 'log_statement' does
> not appear to handle SELECT statements; true?
The "all" setting should.
--
Richard Huxton
Archonet Ltd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dev@archonet.com, lvaningen@esncc.com
Subject: Re: How to Log SELECT Statements Having Errors
In-Reply-To: <4379A053.3010501@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox