Re: Error con logical replication

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
subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test:DETAIL: Waiting
for transactions (approximately 4) older than 301125862 to end.
subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test:LOG: logical
decoding found initial consistent point at 388/56D5A4E8
subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test :DETAIL: Waiting
for transactions (approximately 3) older than 301125877 to end.
subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test:LOG: logical
decoding found consistent point at 388/56D6B888
subtest: 2017-12-21 15:05:16 UTC : replicador(at)xxx test:DETAIL: There are
no old transactions anymore.
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
subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:LOG: logical
decoding found initial starting point at 388/56D33680
subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:DETAIL: Waiting
for transactions (approximately 4) older than 301125862 to end.
subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:LOG: logical
decoding found initial consistent point at 388/56D5A4E8
subtest: 2017-12-21 15:05:17 UTC : replicador(at)xxx test:DETAIL: Waiting
for transactions (approximately 3) older than 301125877 to end.
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.

2017-12-21 10:07 GMT-06:00 Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>:

> motum hesa escribió:
> > Cree la publicación en el servidor 1 de la siguiente forma:
> >
> > create publication pubcummins for table tabla,
> > tabla2,...,tabla29;
> >
> > create user replicador with replication;
> >
> > GRANT USAGE ON SCHEMA tb TO replicador;
> > GRANT SELECT en las 29 tablas;
> >
> > Y en el servidor 2:
> >
> > CREATE SUBSCRIPTION subcummins
> > CONNECTION 'host=dominio port=5432 user=replicador password=xxxx
> > dbname=test'
> > PUBLICATION pubcummins
> > WITH (copy_data = false)
> > ;
> >
> >
> > Probé con copy_data = false y true y los resultados en el uso de CPU
> > siguen siendo los mismo.
>
> ¿y qué dicen los logs?
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>