My problem is that sometimes database stops replying. All I can see is that I have registers in that table
SELECT * FROM pg_logical_slot_get_binary_changes('bdr_17911_6120567807158814813_1_16385__', NULL, 1, 'interactive', 'true')
When I get to this situation, I suppose that means that some transaction have not finish well. So, what can I do to recovery my replication?
Ruth Patricia Melendo Ventura
Software Engineer
TELTRONIC, S.A.U.
T: +34 976 465656 Ext. 179
F: +34 976 465722
www.teltronic.es
De: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] En nombre de Craig Ringer
Enviado el: martes, 17 de marzo de 2015 14:03
Para: Ruth Melendo
CC: pgsql-admin
Asunto: Re: [ADMIN] pgpool + BDR, is it possible?
On 17 March 2015 at 17:52, Ruth Melendo <rmelendo@teltronic.es> wrote:
But now, my dude is about pgpool. Do you think It can work well just as a balancer in this environment?
I cannot tell you that with any confidence without knowing more about the application than is going to be practical. The best I can do is "probably, with the caveats already explained re async multi-master above".
My main troubles from the beginning have been in recovery and I dind´t find detailed doc in that way. Most of times, I need to delete data directory in node 2 and starts init replication again.
"recovery" from what? What are you trying to do?
--