| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Santhosh Kumar <krssanthosh(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Clarification related to BDR |
| Date: | 2020-05-14 08:21:30 |
| Message-ID: | CABUevExMUp69y+y3sUYZ5MNC1vPQ=1cZwn30Beo2W4f++33UYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 14, 2020 at 9:01 AM Santhosh Kumar <krssanthosh(at)gmail(dot)com>
wrote:
> Hi,
> I came across a link published in postgresql, where it is clearly
> mentioned BDR as an open source. When I tried to install BDR for CentOS
> from 2ndQuadrant, the yum repository was not reachable and upon further
> enquiring with 2ndQuadrant, I got a reply from them quoting as follows
>
> "BDR is not open source. We do not have plans to open source this."
>
> Can you please help me understand, why the following news is published in
> "postgresql" with an encouraging message acknowledging BDR as an open
> source? We invested time and effort to use BDR only to understand at a
> later point in time, that it is not. Kindly clarify, if I am missing
> anything.
>
> https://www.postgresql.org/about/news/1689/
>
> [image: image.png]
>
>
>
This news is from 2016. At that time, BDR was open source, but it has since
been closed.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2020-05-14 08:22:22 | Re: Clarification related to BDR |
| Previous Message | Michael Paquier | 2020-05-14 08:04:47 | Re: Check what has been done for a uncommitted prepared transaction |