Re: [BUGS] Replication to Postgres 10 on Windows is broken
Augustine, Jobin <jobin.augustine@openscg.com>
From: "Augustine, Jobin" <jobin.augustine@openscg.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Noah Misch <noah@leadboat.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
pgsql-bugs@postgresql.org, pgsql-hackers@postgresql.org
Date: 2017-08-14T09:01:51Z
Lists: pgsql-bugs, pgsql-hackers
Thank you Tom Lane, This patch fixes the problem. With this patch, streaming replication started working (replication to Windows) (Tested for Linux to Windows replication) -Jobin. On Mon, Aug 14, 2017 at 2:17 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Andres Freund <andres@anarazel.de> writes: > > On 2017-08-11 18:11:03 +0530, Augustine, Jobin wrote: > >> Appears that patch is not helping. > > > That's too bad. Any chance you could install > > https://docs.microsoft.com/en-us/sysinternals/downloads/procmon and > > activate monitoring just for that phase? I think it can export to a text > > file... > > It strikes me that maybe the misuse of io_flag could be contributing > to this: if the walreceiver process's latch were set, we'd end up calling > PQconnectPoll before the socket had necessarily come ready, which would > produce the described symptom. That's grasping at straws admittedly, > because I'm not sure why the walreceiver process's latch would be set > at this point; but it seems like we ought to test a version of the patch > that we believe correct before deciding that we still have a problem. > > To move things along, here's a corrected patch --- Jobin, please test. > > regards, tom lane > > -- *Jobin Augustine* Architect : Production Database Operations *OpenSCG* *phone : +91 9989932600*
Commits
-
Distinguish wait-for-connection from wait-for-write-ready on Windows.
- d7ab908fbab5 10.0 landed
- f3a4d7e7c290 11.0 landed
-
Use asynchronous connect API in libpqwalreceiver
- 1e8a85009447 10.0 cited