Re: jdbc targetServerType=slave with readonly connection - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: jdbc targetServerType=slave with readonly connection
Date
Msg-id CAB=Je-HXDJJtvGNz4Kj0XE=-j2yP+iwp1y789tAerbVRd1bQBQ@mail.gmail.com
Whole thread Raw
In response to jdbc targetServerType=slave with readonly connection  (Vladimír Houba ml. <vladojr@prosoft.sk>)
List pgsql-hackers
>the slave replication server does not seem to be recognized correctly

Could you elaborate on what do you mean by "does not seem to be recognized correctly"?

You might be hitting https://github.com/pgjdbc/pgjdbc/pull/844 , so would you please check if pgjdbc 42.2.0-SNAPSHOT (e.g. https://oss.sonatype.org/content/repositories/snapshots/org/postgresql/postgresql/42.2.0-SNAPSHOT/ ) resolves your issue?

>jdbc driver thinks it is connected to a slave

pjgdbc uses "show transaction_read_only" query to tell master from secondary.

"readOnly=true" connection option is used/activated _after_ the connection, so it should not impact master/secondary selection.

PS. There's 10 second-long (hostRecheckSeconds) cache of the host status. That is, pgjdbc caches master/secondary state of the host for 10 seconds by default, so it might "fail" to identify recently activated secondary. 

Vladimir

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal: alternative psql commands quit and exit
Next
From: Alvaro Herrera
Date:
Subject: Re: proposal: alternative psql commands quit and exit