> Special note for Postgresql users:
> So far I can only reproduce this problem if these
> 3 conditions are met:
> - many connections (20, 25, 27) doing a simple
> SELECT
> - a script running SELECT, CREATE/DROP TABLE/INDEX
> ...
> - a pgAdmin III connected (but without activity)
> (Postgresql version 7.3.6)
Doesn't fail by just changing pgAdmin III with
pgAdmin II.
What's the difference?
III tries first to talk in protocol V3 with the PG
backend. If the backend doesn't understand this
version, which the case for v7.3.6,
pgAdmin falls back to protocol V2 and things go on.
We can see it in the PG log with:
FATAL: unsupported frontend protocol
Does it mean that the backend did something wrong
with the IPCs when refusing V3 ...?
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
