Re: Replication to Postgres 10 on Windows is broken

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, "Augustine, Jobin" <jobin(dot)augustine(at)openscg(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Replication to Postgres 10 on Windows is broken
Date: 2017-08-06 22:04:49
Message-ID: 16046.1502057089@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Here's a prototype patch implementing what Tom outlined.

This bit is flat wrong:

- int io_flag;
+ int io_flag = WL_POSTMASTER_DEATH | WL_LATCH_SET;

io_flag has to be *just* the I/O condition, because we use it in a test
after the WaitLatchOrSocket call.

> Anybody have an opinion about adding ifs for WL_SOCKET_CONNECTED to
> !win32 implementations rather than redefining it to WL_SOCKET_WRITEABLE?

I fear it would complicate matters greatly, because you'd have to figure
out which of the two flags to signal back after detecting socket writable.
I think defining it as equal to WL_SOCKET_WRITEABLE is fine.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2017-08-06 22:10:42 Re: Replication to Postgres 10 on Windows is broken
Previous Message Andres Freund 2017-08-06 21:55:21 Re: Replication to Postgres 10 on Windows is broken

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-08-06 22:10:42 Re: Replication to Postgres 10 on Windows is broken
Previous Message Andres Freund 2017-08-06 21:55:21 Re: Replication to Postgres 10 on Windows is broken