From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
---|---|
To: | Hellmuth Vargas <hivs77(at)gmail(dot)com> |
Cc: | Lista Postgres ES <pgsql-es-ayuda(at)postgresql(dot)org> |
Subject: | Re: Can not upload timeline file from primary history server |
Date: | 2020-07-18 19:09:00 |
Message-ID: | CAJGNTeMqtu1BYuGTxauo3TBiM1tD6eOqtvt4H-YLf1d6jNk8yg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
>
> El sáb., 18 de jul. de 2020, 1:17 p. m., Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> escribió:
>>
>> On Tue, 7 Jul 2020 at 08:24, Hellmuth Vargas <hivs77(at)gmail(dot)com> wrote:
>> >
>> > Hola Lista
>> >
>> > Al crear una replica con pg_basebackup obtuve el siguiente error:
>> >
>> > could not receive timeline history file from the primary server: ERROR: could not open file "pg_wal/00000003.history
>> >
>>
>> Saludos,
>>
>> Que raro! como promoviste cada réplica? usaste pg_ctl promote?
>>
On Sat, 18 Jul 2020 at 13:30, Hellmuth Vargas <hivs77(at)gmail(dot)com> wrote:
>
> Hola Jaime
>
> Si señor, con promote en todos los casos
hay actividad en los servidores promovidos? modificación de datos o
solo lectura? que tiempo transcurre entre cada nuevo servidor
promovido y que crees una nueva réplica?
me gustaría hacer un experimento para ver si me ocurre lo mismo
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Hellmuth Vargas | 2020-07-18 21:23:48 | Re: Can not upload timeline file from primary history server |
Previous Message | Hellmuth Vargas | 2020-07-18 18:30:37 | Re: Can not upload timeline file from primary history server |