Re: bdr appears to be trying to replicate to itself
От | Cj B |
---|---|
Тема | Re: bdr appears to be trying to replicate to itself |
Дата | |
Msg-id | 2F4DC8FE-E749-4B07-BBBA-EB3B5C4ACA96@gmail.com обсуждение исходный текст |
Ответ на | Re: bdr appears to be trying to replicate to itself (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: bdr appears to be trying to replicate to itself
|
Список | pgsql-general |
Hi, Yes, I posted on github because I wasn’t sure where to post. And the reason I’m posting here is because I’m not clear aboutthe answer "Drop the slot bdr_16385_6188730679935789649_1_16385__ on the first host.” Do this just mean to select pg_drop_replication_slot(‘bdr_16385_6188730679935789649_1_16385__’) What impact will this have? Thanks Cj B > On Nov 16, 2015, at 8:31 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > Cj B wrote: >> I noticed a very strange issue starting about 20 days ago and my pg_xlog has just been filling up since then. > > For reference, this was also asked on github, and answered there. > See https://github.com/2ndQuadrant/bdr/issues/143 > > > -- > Álvaro Herrera http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-general по дате отправления: