Lin, B (Bill) wrote:
>Does that mean 8.1.3 works fine on other PCs you have, but not this
one?
Yes, it is works fine with other PCs which do not have dual processor.
(I can not find another machine has dual processor here)
Ah, does your problem match what is being discussed here?
http://archives.postgresql.org/pgsql-performance/2006-03/msg00032.php
If so, that suggests to me that there must be either:
1. A different library on the problem machine.
No, same library are used.
2. Some process (firewall/antivirus) that is occasionally interfering
with communication.
No firewall/antivirus was running
Three things suggest themselves to me:
1. Make sure there aren't any known issues with the jdbc driver version
you have http://jdbc.postgresql.org/
Seems not, but not sure about this one:
http://jdbc.postgresql.org/todo.html#Known+Bugs
[bugs] Deallocating large numbers of server side statements can break
the connection by filling network buffers. This is a very, very low
probability bug, but it is still possible.
Hmm - doesn't sound like that's it.
Actually, if using jdbc driver version 7.4 against database 8.1.3, this
problem will not happen.
It seems it is a bug relate with jdbc driver for a dual processor.
Or possibly lower down even.
2. Check if there is anything unusual about the problem machine
Nothing unusual
3. Try running the client on the problem machine and the database on
another, then the other way around. Does this change anything?
I tried both way and this problem seems never happen.
Hmm - I'd have expected it to fail in one direction but not the other.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
