>  I get this problem on my dev (Windows/7.4/Cygwin) environment.  But now 
> I see that it's also have this problem on my production env.  Yes I 
> tought I was maybe just a cygwin/Windows problem .. apparently not :-((((

Care to try again with logging enabled on the PostgreSQL side within the
development environment?

log_statement = true
log_duration = true
log_connections = on

Then run it via Java and from pgAdminIII and send us the two log
snippets as attachments?


---------------------------(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

Reply via email to