hi
i searched the archives and found one guy complaining about it in
march. yet - we recently installed 8.0.2 and the problem is still
there.
we moved back to drivers for 7.4, but it looks weird - use postgresql
8.0, and drivers to 7.4.
it there anybody working on this issue?

if you're not familiar with the problem:
using jdbc for postgresql 8.0 it renders postgresql not logging
duration: lines into logs. despite the fact that i have
log_duration = true
log_statement = 'all'

driver for 7.4 works fine.

depesz

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

This is an artifact of using the v3 protocol and prepared
statements; it is a known issue.

Although, I've never heard of it not logging duration.

Dave
On 11-Jun-05, at 2:18 AM, hubert depesz lubaczewski wrote:

> hi
> i searched the archives and found one guy complaining about it in
> march. yet - we recently installed 8.0.2 and the problem is still
> there.
> we moved back to drivers for 7.4, but it looks weird - use postgresql
> 8.0, and drivers to 7.4.
> it there anybody working on this issue?
>
> if you're not familiar with the problem:
> using jdbc for postgresql 8.0 it renders postgresql not logging
> duration: lines into logs. despite the fact that i have
> log_duration = true
> log_statement = 'all'
>
> driver for 7.4 works fine.
>
> depesz
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan
> if your
> joining column's datatypes do not match
>
>


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings