| From: | Rob Kirkbride <rob(at)rkcomputing(dot)co(dot)uk> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: More Verbose Logging of Statements |
| Date: | 2005-11-10 16:19:53 |
| Message-ID: | 43737329.1050606@rkcomputing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka wrote:
>
>
> On Thu, 10 Nov 2005, Rob Kirkbride wrote:
>
>> I've been trying to understand the documentation at
>> http://www.postgresql.org/docs/8.0/static/runtime-config.html but I
>> can't get it to put into my logfile the actual contents of prepared
>> statement parameters. I just get $1, $2 etc. I'd like to show me what
>> those are either in the actual line or below I don't mind which.
>>
>
> No, the JDBC driver uses the new extended query protocol by default
> which the server does not log very well. You could make the driver
> fallback to the older protocol by using the URL parameter
> ?protocolVersion=2 which is logged fully, but then you're not really
> testing the same thing if you are trying to debug a problem or do a
> performance analysis.
>
OK. Thanks. :-( It's to debug things like where you get constraint
violation on keys but you don't what the key was. I guess I'd have to
try and get the client to do it - hibernate - but this tends to print $s
as well!
Thanks,
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-11-10 16:20:36 | Re: Getting param names |
| Previous Message | Kris Jurka | 2005-11-10 16:15:44 | Re: More Verbose Logging of Statements |