| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Steve Pribyl <Steve(dot)Pribyl(at)akunacapital(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR workers exiting? |
| Date: | 2015-10-13 03:37:22 |
| Message-ID: | CAMsr+YHM6QYReR=eCwpztn7=jrkPa_Ch7Zt6C580645=nM7Ngw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
BDR is currently memory-limited for extremely large transactions. At a
guess, I'd say one of your big tables is large enough that the logical
decoding facility BDR uses can't keep track of the transaction
properly.
There's no hard limit, it depends on details of the transaction and a
number of other variables, but "many tens or hundreds of GB" is
generally too much.
If I was to load such a big DB, I'd probably do it with ETL tools that
could split up the load and do it progressively.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2015-10-13 04:51:42 | Re: BDR: no free replication state could be found |
| Previous Message | Victor Blomqvist | 2015-10-13 02:53:43 | Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type: |