Horton

Re: [BUGS] Replication to Postgres 10 on Windows is broken

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, jobin.augustine@openscg.com, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Noah Misch <noah@leadboat.com>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-08-17T01:32:03Z
Lists: pgsql-bugs, pgsql-hackers 
On Thu, Aug 17, 2017 at 9:15 AM, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>> He meant logical replication,
>
> Oh I could not find he meant logical replication in the original
> report.

The second message of the thread says so, but the first does not
mention logical replication at all.
>From here are mentioned PG 9.6 and pg_basebackup:
https://www.postgresql.org/message-id/CAHBggj8g2T+ZDcACZ2FmzX9CTxkWjKBsHd6NkYB4i9Ojf6K1Fw@mail.gmail.com.
Explaining the confusion.
-- 
Michael

Commits

  1. Distinguish wait-for-connection from wait-for-write-ready on Windows.

  2. Use asynchronous connect API in libpqwalreceiver