Re: log_statement and PREPARE - Mailing list pgsql-general

From Tom Lane
Subject Re: log_statement and PREPARE
Date
Msg-id 9084.1189131905@sss.pgh.pa.us
Whole thread Raw
In response to Re: log_statement and PREPARE  (brian <brian@zijn-digital.com>)
Responses Re: log_statement and PREPARE  (brian <brian@zijn-digital.com>)
List pgsql-general
brian <brian@zijn-digital.com> writes:
> The only hint of a prepared statement being logged is when there's an
> error. eg:

> <2007-09-05 17:35:22 EDT>ERROR:  duplicate key violates unique
> constraint "auth_member_id_key"
> <2007-09-05 17:35:22 EDT>STATEMENT:  EXECUTE
> mdb2_statement_pgsqla0e8d35156e904f9581ac790eb917b98 (A_HASH_HERE, 5271)

That looks like an EXECUTE to me.  If you want EXECUTEs to be logged
conditionally based on what they are executing, you need 8.2.

            regards, tom lane

pgsql-general by date:

Previous
From: Ow Mun Heng
Date:
Subject: Re: Column as arrays.. more efficient than columns?
Next
From: Ow Mun Heng
Date:
Subject: Re: Column as arrays.. more efficient than columns?