Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z7SYm-0002hJ-HP for pgsql-admin@arkaria.postgresql.org; Tue, 23 Jun 2015 18:04:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z7SYl-0003hP-Oo for pgsql-admin@arkaria.postgresql.org; Tue, 23 Jun 2015 18:04:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Z7SWM-0001Rq-DJ for pgsql-admin@postgresql.org; Tue, 23 Jun 2015 18:02:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Z7SWI-0002Gm-OP for pgsql-admin@postgresql.org; Tue, 23 Jun 2015 18:02:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t5NI1wLo004991; Tue, 23 Jun 2015 14:01:59 -0400 From: Tom Lane To: Sanjay Veeramachaneni cc: pgsql-admin@postgresql.org Subject: Re: pg_dump: Error message from server: lost synchronization with server: got messag e type "d", In-reply-to: References: <1435069522258-5854831.post@n5.nabble.com> <2018.1435070223@sss.pgh.pa.us> <2164.1435070683@sss.pgh.pa.us> Comments: In-reply-to Sanjay Veeramachaneni message dated "Tue, 23 Jun 2015 09:52:39 -0700" Date: Tue, 23 Jun 2015 14:01:58 -0400 Message-ID: <4990.1435082518@sss.pgh.pa.us> X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Sanjay Veeramachaneni writes: > Here is the version for libpq Well, that list is pretty opaque, because you've got several different entries for libpq-dev and nothing for libpq proper ... but at least one of those is a version that would contain the bug I mentioned. Having said that, we've never seen a report of this bug visibly manifesting on Linux, only on Windows. So if that is what's biting you there must be something unusual about your environment. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin