Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: pg_dump: Error message from server: lost synchronization with
 server: got messag e type "d",
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <2164.1435070683@sss.pgh.pa.us>
Date: Tue, 23 Jun 2015 09:16:17 -0600
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08D846A5-E1F4-40AC-BE2C-661243EB44DF@elevated-dev.com>
References: <1435069522258-5854831.post@n5.nabble.com>
 <2018.1435070223@sss.pgh.pa.us> <2164.1435070683@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

I noted this part of the bug:

> The reported cases involve Windows, which perhaps has
>    different timing behavior than other platforms.

Many years ago, I move some code from UNIX to Windows (XP). On UNIX, I'd ju=
st made sure that I was making network write calls with decent-sized buffer=
s of at least a few multiples of packet size, and it would come pretty clos=
e to saturating the network. On windows, the same approach with same buffer=
 sizes had 1/10th the network performance.

So, yeah, Windows had "different timing behavior" to say the least.

--=20
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin