| From: | motum hesa <motums(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Lista PostgreSQL <pgsql-es-ayuda(at)postgresql(dot)org> |
| Subject: | Re: Error con logical replication |
| Date: | 2017-12-21 17:21:08 |
| Message-ID: | CAJu20Aj_GybPriW5d3=6Y3NBxHYjxt3c+_yHqhVYk-rnKc9BMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
2017-12-21 10:17 GMT-06:00 Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>:
> 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.
>
Agregado
>
> > 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.
>
Después de activarlo, esto muestra el log:
58304: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :LOG:
logical decoding found consistent point at 389/F3FBC478
58304: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :DETAIL:
There are no running transactions.
58305: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :LOG:
starting logical decoding for slot "subcummins"
58305: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :DETAIL:
streaming transactions committing after 389/F3FBC4B0, reading WAL from
389/F3FBC478
58305: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :LOG:
logical decoding found consistent point at 389/F3FBC478
58305: subtest: 2017-12-21 17:12:28 UTC : replicador(at)xxx test :DETAIL:
There are no running transactions.
>
> > 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?
>
Esto es lo que muestra pg_stat_activity para el usuario replicador:
[image: Imágenes integradas 1]
En top se ve el proceso wal_sender:
[image: Imágenes integradas 2]
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-12-21 17:31:53 | Re: Error con logical replication |
| Previous Message | Alvaro Herrera | 2017-12-21 16:17:51 | Re: Error con logical replication |