From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 hard crash problem |
Date: | 2006-09-05 21:47:56 |
Message-ID: | 28348.1157492876@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>> Fail in what way. Hang, not connect, or get an error msg?
> Just verified with customer. Once the problem occurs the first time, the
> customer will continually get the same error message for each subsequent
> connection attempt:
> server sent data ("D" message) without prior row description ("T" message)
During the connection attempt? I don't think libpq can report that
message until it tries to do a regular query (might be wrong though).
Is the client using some application that's going to issue a query
immediately on connecting?
It would be useful to turn on log_connections and log_statement (and
perhaps crank log_min_messages all the way up to DEBUG5) to see if we
can get anything in the postmaster log giving a hint what actually
happens here. A TCP sniff of the connection attempt traffic would be
pretty useful too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2006-09-05 21:58:06 | Re: BUG #2600: dblink compile with SSL missing libraries |
Previous Message | Bruce Momjian | 2006-09-05 21:47:00 | Re: Open items for 8.2 |