From: | "Augustine, Jobin" <jobin(dot)augustine(at)openscg(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Replication to Postgres 10 on Windows is broken |
Date: | 2017-08-11 12:41:03 |
Message-ID: | CAHBggj-YZ6vd7oeZGebbJJbSaYXRjwB8rd9Un92OjJWX7VaQmg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Appears that patch is not helping.
Errors like below are still appearing in the log
===============================
2017-08-11 12:22:35 UTC [2840]: [1-1] user=,db=,app=,client= FATAL: could
not connect to the primary server: could not send data to server: Socket is
not connected (0x00002749/10057)
could not send startup packet: Socket is not connected
(0x00002749/10057)
2017-08-11 12:22:40 UTC [1964]: [1-1] user=,db=,app=,client= FATAL: could
not connect to the primary server: could not send data to server: Socket is
not connected (0x00002749/10057)
could not send startup packet: Socket is not connected
(0x00002749/10057)
2017-08-11 12:22:45 UTC [248]: [1-1] user=,db=,app=,client= FATAL: could
not connect to the primary server: could not send data to server: Socket is
not connected (0x00002749/10057)
could not send startup packet: Socket is not connected
(0x00002749/10057)
===============================
On Fri, Aug 11, 2017 at 7:28 AM, Augustine, Jobin <
jobin(dot)augustine(at)openscg(dot)com> wrote:
> I am in an effort to create independent build environment on Windows to
> test the patch from Andres.
> I shall come back with result possibly in another 24 hours.
>
> -Jobin
>
> On Fri, Aug 11, 2017 at 7:25 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>> On 2017-08-10 18:51:07 -0700, Noah Misch wrote:
>> > On Tue, Aug 08, 2017 at 07:25:37PM -0400, Peter Eisentraut wrote:
>> > > On 8/7/17 21:06, Noah Misch wrote:
>> > > >> That would fit. Until v10 (commit 1e8a850), PQconnectStart() had
>> no in-tree
>> > > >> callers outside of libpq itself.
>> > > > [Action required within three days. This is a generic
>> notification.]
>> > > >
>> > > > The above-described topic is currently a PostgreSQL 10 open item.
>> Peter,
>> > > > since you committed the patch believed to have created it, you own
>> this open
>> > > > item.
>> > >
>> > > I don't think I can usefully contribute to this. Could someone else
>> > > take it?
>> >
>> > If nobody volunteers, you could always resolve this by reverting
>> 1e8a850 and
>> > successors.
>>
>> I've volunteered a fix nearby, just can't test it. I don't think we can
>> require committers to work on windows.
>>
>> - Andres
>>
>
>
>
> --
>
> *Jobin Augustine*
> Architect : Production Database Operations
>
>
> *OpenSCG*
>
>
> *phone : +91 9989932600*
>
--
*Jobin Augustine*
Architect : Production Database Operations
*OpenSCG*
*phone : +91 9989932600*
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2017-08-11 13:04:27 | Re: BUG #14776: ecpg 4.12.0 issues with macros containing line continued blocks |
Previous Message | Thomas S. Chin | 2017-08-11 09:04:45 | Re: BUG #14776: ecpg 4.12.0 issues with macros containing line continued blocks |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2017-08-11 12:53:36 | Re: Funny WAL corruption issue |
Previous Message | Álvaro Hernández Tortosa | 2017-08-11 12:31:58 | Re: SCRAM protocol documentation |