Re: Revive targetServerType=preferPrimary feature

Поиск
Список
Период
Сортировка
От Mukhin, Dmitriy
Тема Re: Revive targetServerType=preferPrimary feature
Дата
Msg-id 6290B456-D7ED-4E30-9466-AD22CDBD4C4D@verisign.com
обсуждение исходный текст
Ответ на Revive targetServerType=preferPrimary feature  ("Mukhin, Dmitriy" <dmukhin@verisign.com>)
Список pgsql-jdbc
I have created https://github.com/pgjdbc/pgjdbc/pull/2483 per our conversation below. Can you please review it and let
meknow if anything else needs to be done?
 

Thanks,

Dmitriy


From: Dave Cramer <pg@fastcrypt.com>
Date: Thursday, March 24, 2022 at 10:42 AM
To: "Mukhin, Dmitriy" <dmukhin@verisign.com>
Cc: "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Subject: Re: Revive targetServerType=preferPrimary feature

> On Thu, 24 Mar 2022 at 10:35, Mukhin, Dmitriy <dmukhin(at)verisign(dot)com> wrote:
>
> > Hi All,
> >
> > In 2019, there was a discussion on implementing the
> > targetServerType=preferPrimary JDBC driver parameter feature (see here: How
> > to send queries to master and failover to slave ?
> >
<https://www.postgresql.org/message-id/VI1PR05MB5295BA974B84191217A6A613BC760%40VI1PR05MB5295.eurprd05.prod.outlook.com>)
> > and a Pull Request created for that (
> > https://github.com/pgjdbc/pgjdbc/pull/1430 ). The project I’m working on
> > would greatly benefit from merging this PR and apparently there were other
> > people that requested this feature before. Can we revive this PR and
> > reconsider its merging? Alternatively, I can create a fresh PR with the
> > same changes against current master branch and submit it for review. Please
> > let me know what I can do to make this change happen.
> >
> > Thank you!
> >
> > Dmitriy Mukhin
> >
>
> It needs to be cleaned up so yes, please create a new PR.
>
> Thanks,
>
> Dave
>


В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Dave Cramer
Дата:
Сообщение: [pgjdbc/pgjdbc] aa1f58: Remove isDeprecated from PGProperty. It was origin...
Следующее
От: Blake McBride
Дата:
Сообщение: Re: JDBC: ERROR: portal "C_2" does not exist