| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_dump: Error message from server: lost synchronization with server: got messag e type "d", |
| Date: | 2015-06-23 15:16:17 |
| Message-ID: | 08D846A5-E1F4-40AC-BE2C-661243EB44DF@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 just made sure that I was making network write calls with decent-sized buffers of at least a few multiples of packet size, and it would come pretty close 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.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sanjay Veeramachaneni | 2015-06-23 15:42:34 | Re: pg_dump: Error message from server: lost synchronization with server: got messag e type "d", |
| Previous Message | Tom Lane | 2015-06-23 14:44:43 | Re: pg_dump: Error message from server: lost synchronization with server: got messag e type "d", |