| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | milist ujang <ujang(dot)milist(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR, limit number of groups in a cluster |
| Date: | 2017-09-11 01:55:29 |
| Message-ID: | CAMsr+YGFDZdk=F9zq-j7RcCJ3107+_W89_HK0-fURpzTOMjORA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11 September 2017 at 09:32, milist ujang <ujang(dot)milist(at)gmail(dot)com> wrote:
> Hi all,
>
> Based on the docs and look at the processes, it seems 1 wal sender on each
> node per group.
>
> If there is scenario of consolidating many databases (say hundreds) into 1
> database (in this central cluster there are hundreds wal sender), what is
> the limit number of groups?
>
It's not a use case I've paid much attention to. I expect it'll be limited
by performance and memory, rather than have any firm limit.
Maybe you should look into pglogical. This seems like a weird use for BDR.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Güttler | 2017-09-11 13:25:26 | Final pg_dumpall should happen in Single-User-Mode |
| Previous Message | milist ujang | 2017-09-11 01:32:10 | BDR, limit number of groups in a cluster |