Re: Replication issue

On 4/17/20 7:47 AM, Sonam Sharma wrote:
> Yes, you are right. It's for connection failover from application end. I 
> have set up db replication using repmgr. Version : 9.5
> 

Can you reach the database crowd at host 172.29.195.216:50001 using psql 
or some other client?

> 
> 
> On Fri, Apr 17, 2020, 8:15 PM Julien Rouhaud <rjuju123@gmail.com 
> <mailto:rjuju123@gmail.com>> wrote:
> 
>     On Fri, Apr 17, 2020 at 4:02 PM Adrian Klaver
>     <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      >
>      > On 4/17/20 6:31 AM, Sonam Sharma wrote:
>      > > I have setup db replication. And added below parameter in jdbc
>     file .
>      > > The connection is failing and it's throwing error like db
>     doesn't exist
>      > > on secondary server.
>      > >
>      > >
>
jdbc:postgresql://<primaryhost>:50001,172.29.195.216:50001/crowd?targetServerType=master&reWriteBatchedInserts=true
>     <http://172.29.195.216:50001/crowd?targetServerType=master&reWriteBatchedInserts=true>
>      > >
>     <http://172.29.195.216:50001/crowd?targetServerType=master&reWriteBatchedInserts=true>
>      > >
>      > > .PSQLException: FATAL: database ",172.29.195.216
>      > > <tel:+17229195216>:50001/crowd" does not exist
>      > >
>      > >
>      > > Can someone help on this issue?
>      > >
>      >
>      > Set up replication using what?
>      >
>      > The URL above does not look correct to me. Pretty sure the ','
>     does not
>      > belong there.
> 
>     This was probably intended to be the "connection failover" feature
>     (https://jdbc.postgresql.org/documentation/head/connect.html).  I'm
>     wondering if the issue is just that the driver is too old to support
>     that, but I have no idea when this was introduced in jdbc.
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com