Re: Win32 hard crash problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Win32 hard crash problem
Date
Msg-id 28348.1157492876@sss.pgh.pa.us
Whole thread Raw
In response to Re: Win32 hard crash problem  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Win32 hard crash problem  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Win32 hard crash problem  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Win32 hard crash problem  ("Magnus Hagander" <mha@sollentuna.net>)
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Open items for 8.2
Next
From: Alvaro Herrera
Date:
Subject: Re: Win32 hard crash problem