| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | motum hesa <motums(at)gmail(dot)com> |
| Cc: | Lista PostgreSQL <pgsql-es-ayuda(at)postgresql(dot)org> |
| Subject: | Re: Error con logical replication |
| Date: | 2017-12-21 16:17:51 |
| Message-ID: | 20171221161751.ry2324wvvsmb7rtn@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
motum hesa escribió:
> Después de activarla sólo mencionan esto:
>
> subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test:LOG: logical
> decoding found initial starting point at 388/56D33680
Por favor agrega %p a tu log_line_prefix.
> subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:LOG: starting
> logical decoding for slot "subcummins"
> subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test :DETAIL: streaming
> transactions committing after 388/56D6B8D0, reading WAL from 388/56D33680
Hasta aquí todo bien, creo ...
> subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:LOG: logical
> decoding found initial starting point at 388/56D33680
pero no entiendo por qué volvemos a este paso una y otra vez.
> subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:LOG: logical
> decoding found consistent point at 388/56D6B888
> subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:DETAIL: There are
> no old transactions anymore.
En este punto deberían haber bgworkers, aunque si le dijiste
sync_data=false no habrá sync workers, ¿qué dice pg_stat_activity?
¿qué procesos están usando CPU?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | motum hesa | 2017-12-21 17:21:08 | Re: Error con logical replication |
| Previous Message | motum hesa | 2017-12-21 16:12:22 | Re: Error con logical replication |