Обсуждение: BDR, 9.4 release schedule, PostgreSQL in Azure, pgPool-II

Поиск
Список
Период
Сортировка

BDR, 9.4 release schedule, PostgreSQL in Azure, pgPool-II

От
Тарас Савчук
Дата:

Hi All :)

 

A few questions from a newbie.

 

1. Use someone BDR in production (https://wiki.postgresql.org/wiki/BDR_Project)?

2. When ~ is expected to release 9.4?

3. Use someone PostgreSQL in Azure and can give any advice?

4. Do I understand correctly that the closest analog of mysql-proxy – it’s pgPool-II. The scheme is very simple - every frontend with the code works with own database’s instance, and use another one instance of DB only in case of problems with main (own) DB.

 

DB under fairly simple application. The desire to use BDR dictated by scaling in breadth on comfortable on the price / quality instances and not be fooled unreliability of individual VM in Azure (ie, at the minimum, we have two VMs with PostgreSQL in one availability set of Azure).

 

Thanks in advance!

 

P.S. Sorry for my bad English )))

 

--
Savchuk Taras

 

Re: BDR, 9.4 release schedule, PostgreSQL in Azure, pgPool-II

От
Tatsuo Ishii
Дата:
> Hi All :)
>
> A few questions from a newbie.
>
> 1. Use someone BDR in production (https://wiki.postgresql.org/wiki/BDR_Project)?
> 2. When ~ is expected to release 9.4?

I don't think it's in 9.4.

> 3. Use someone PostgreSQL in Azure and can give any advice?

I have no experience with Azure. So no idea.

> 4. Do I understand correctly that the closest analog of mysql-proxy - it's pgPool-II. The scheme is very simple -
everyfrontend with the code works with own database's instance, and use another one instance of DB only in case of
problemswith main (own) DB. 

I have no experience with mysql-proxy. However quick googling suggests
that mysql-proxy is resemble to pgpool-II except that pgpool-II has
failover functionality, while mysql-proxy not.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> DB under fairly simple application. The desire to use BDR dictated by scaling in breadth on comfortable on the price
/quality instances and not be fooled unreliability of individual VM in Azure (ie, at the minimum, we have two VMs with
PostgreSQLin one availability set of Azure). 
>
> Thanks in advance!
>
> P.S. Sorry for my bad English )))
>
> --
> Savchuk Taras
>