Re: jdbc targetServerType=slave with readonly connection

Поиск
Список
Период
Сортировка
От Vladimir Sitnikov
Тема Re: jdbc targetServerType=slave with readonly connection
Дата
Msg-id CAB=Je-HXDJJtvGNz4Kj0XE=-j2yP+iwp1y789tAerbVRd1bQBQ@mail.gmail.com
обсуждение исходный текст
Ответ на jdbc targetServerType=slave with readonly connection  (Vladimír Houba ml. <vladojr@prosoft.sk>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: proposal: alternative psql commands quit and exit
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: proposal: alternative psql commands quit and exit