| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Augustine, Jobin" <jobin(dot)augustine(at)openscg(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Replication to Postgres 10 on Windows is broken |
| Date: | 2017-08-13 21:17:17 |
| Message-ID: | 22868.1502659037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Augustine, Jobin" <jobin(dot)augustine(at)openscg(dot)com> writes:
> 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)
BTW, I notice that this is a bit different from your first report, because
that mentioned "could not send SSL negotiation packet" rather than "could
not send startup packet". If the initial report was about a setup in
which SSL was enabled, and in this report's setup it isn't, then that
difference is unsurprising; but otherwise it needs explanation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-13 21:22:22 | Re: [HACKERS] Replication to Postgres 10 on Windows is broken |
| Previous Message | Tom Lane | 2017-08-13 20:55:33 | Re: [BUGS] Replication to Postgres 10 on Windows is broken |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-13 21:22:22 | Re: [HACKERS] Replication to Postgres 10 on Windows is broken |
| Previous Message | Tom Lane | 2017-08-13 20:55:33 | Re: [BUGS] Replication to Postgres 10 on Windows is broken |