From: | "Lin, B \(Bill\)" <b(dot)lin(at)dl(dot)ac(dot)uk> |
---|---|
To: | "Richard Huxton" <dev(at)archonet(dot)com> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Random hang during commit |
Date: | 2006-03-15 11:55:12 |
Message-ID: | 77673C9ECE12AB4791B5AC0A7BF40C8F025A9496@exchange02.fed.cclrc.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Yes, It looks exactly same as
http://archives.postgresql.org/pgsql-performance/2006-03/msg00032.php
Only different is: in my case it happens in every 2 mins :)
(I just found it is not only happen during commit, it could be during
other sql call randomly)
Thank you very much, at least I know what is the problem now.
Bill
-----Original Message-----
From: Richard Huxton [mailto:dev(at)archonet(dot)com]
Sent: 15 March 2006 11:27
To: Lin, B (Bill)
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] Random hang during commit
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
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Sunday | 2006-03-15 17:48:59 | Re: Large join runs out of memory in 8.1 |
Previous Message | Richard Huxton | 2006-03-15 11:26:38 | Re: Random hang during commit |