Re: [BUGS] Replication to Postgres 10 on Windows is broken
От | Noah Misch |
---|---|
Тема | Re: [BUGS] Replication to Postgres 10 on Windows is broken |
Дата | |
Msg-id | 20170806062634.GA3180536@rfd.leadboat.com обсуждение исходный текст |
Ответ на | [BUGS] Replication to Postgres 10 on Windows is broken ("Augustine, Jobin" <jobin.augustine@openscg.com>) |
Ответы |
Re: [BUGS] Replication to Postgres 10 on Windows is broken
|
Список | pgsql-bugs |
On Fri, Aug 04, 2017 at 11:23:43AM +0530, Augustine, Jobin wrote: > *Summary:* > Replica / Slave on Windows fails to conenct to Master. > > *Scenario:* > Master: PostgreSQL 10 (beta1,beta2), Any OS (Linux, Windows, Mac) > Slave : PostgreSQL 10 (beta1,beta2), Windows (Any MS Windows OS) > Slave must be on Windows Machine running on a different server than the > Master > > > *Steps to reproduce:* > 1. Setup a Postgres 10betaX master database can be on any platform > (Linux/Windows/Mac) > 2. Try to setup a streaming replica on any of the MS Windows running a > different Server than the master I've added this as an open item. Confirmed in this setup: -- Server Debian 9 PostgreSQL 10beta2 from apt.postgresql.org edit postgresql.conf to allow remote connections edit pg_hba.conf to allow remote connections create replication user w/ password -- Client Windows Server 2016 postgresql-10.0-beta2-windows-x64-binaries.zip from EnterpriseDB pg_basebackup -h myserver -D datadir -X stream -R install ordinary *.conf postgres -D datadir > Stand alone tools like psql, pg_basebackup, pg_recivewal etc are > successful in connecting to primary server and perform their > functionalities. I can confirm each of those, too. I don't, however, see a smoking gun among commits. Would you bisect the commits since 9.6 and see which one broke things? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: