From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Lane Van Ingen <lvaningen(at)esncc(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: How to Log SELECT Statements Having Errors |
Date: | 2005-11-15 08:46:11 |
Message-ID: | 4379A053.3010501@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2005-11-15 08:52:58 | Re: How to Log SELECT Statements Having Errors |
Previous Message | Lane Van Ingen | 2005-11-15 01:17:47 | How to Log SELECT Statements Having Errors |