Re: Proposal: Implement failover on libpq connect level.

Поиск
Список
Период
Сортировка
От ''Victor Wagner *EXTERN*' *EXTERN*' *EXTERN*
Тема Re: Proposal: Implement failover on libpq connect level.
Дата
Msg-id 20150819144526.GA3623@wagner.pp.ru
обсуждение исходный текст
Ответ на Re: Proposal: Implement failover on libpq connect level.  (Simon Riggs <simon@2ndQuadrant.com>)
Ответы Re: Proposal: Implement failover on libpq connect level.  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Список pgsql-hackers
On 2015.08.19 at 15:35:17 +0100, Simon Riggs wrote:

> 
> I think we do need some way of saying that a readonly connection is OK. So

I had such thing in my propsal (boolean parameter readonly). 
But haven't yet checked if it is compatible with jdbc syntax.

> the default would be to connect to each in turn until we find the master.
> It should keep retrying for a period of time since for a short period it is
> possible there is no master. If you specify readonly, then a connection to

It is very important addition  - to specify that if no host is able to
establish read-write session, we should retry and give a chance for
sever administration to promote one of standbys to master. Probably
there should be additional timeout parameter (we have
connection_timeout, and this would be failover_timeout) with some
reasonaable default.




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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Proposal: Implement failover on libpq connect level.
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows