Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 225F1B5DBD3 for ; Mon, 16 May 2011 14:56:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 86772-01-6 for ; Mon, 16 May 2011 17:56:47 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by mail.postgresql.org (Postfix) with ESMTP id 52FF2B5DBDF for ; Mon, 16 May 2011 14:56:47 -0300 (ADT) Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta12.westchester.pa.mail.comcast.net with comcast id kHuZ1g0061GhbT85CHwnLu; Mon, 16 May 2011 17:56:47 +0000 Received: from sz0093.wc.mail.comcast.net ([76.96.58.151]) by omta07.westchester.pa.mail.comcast.net with comcast id kHwn1g01G3FmDic3THwn3r; Mon, 16 May 2011 17:56:47 +0000 Date: Mon, 16 May 2011 17:56:47 +0000 (UTC) From: Lou Picciano To: pgsql-admin Message-ID: <1194625814.262792.1305568607296.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> In-Reply-To: <1056249676.262729.1305568545679.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Subject: Session handshaking: 'Incomplete startup packets' message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_262791_1044233414.1305568607295" X-Originating-IP: [76.117.178.80] X-Mailer: Zimbra 6.0.5_GA_2431.RHEL5_64 (ZimbraWebClient - SAF3 (Mac)/6.0.5_GA_2427.RHEL4) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.907 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RFC_ABUSE_POST=0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201105/100 X-Sequence-Number: 37537 ------=_Part_262791_1044233414.1305568607295 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit PG friends, For a small handful of our clients, we see an 'Incomplete startup packets' message in our logs, just at the beginning of a connection session. It appears to do no damage to the session, which otherwise continues to do its work without error. We're trying to dig deeper on this but, so far, it seems to be coming only from Windows clients - and perhaps even only from Vista clients. Had originally thought it was being caused by load-balancing or other specific hardware less common at most of our client sites, but I think we've ruled that out. We continue to research it. Meanwhile: anyone else seeing this, or could shed some light on its origin? Lou ------=_Part_262791_1044233414.1305568607295 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
PG friends,

For a small handful of our clients, we see an 'Incomplete startup packets' message in our logs, just at the beginning of a connection session. It appears to do no damage to the session, which otherwise continues to do its work without error.

We're trying to dig deeper on this but, so far, it seems to be coming only from Windows clients - and perhaps even only from Vista clients. Had originally thought it was being caused by load-balancing or other specific hardware less common at most of our client sites, but I think we've ruled that out. We continue to research it.

Meanwhile: anyone else seeing this, or could shed some light on its origin?

Lou
------=_Part_262791_1044233414.1305568607295--