Re: log_statement and PREPARE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: brian <brian(at)zijn-digital(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: log_statement and PREPARE
Date: 2007-09-07 02:25:05
Message-ID: 9084.1189131905@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

brian <brian(at)zijn-digital(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ow Mun Heng 2007-09-07 02:26:26 Re: Column as arrays.. more efficient than columns?
Previous Message Ow Mun Heng 2007-09-07 02:21:06 Re: Column as arrays.. more efficient than columns?