Logical replication 'possible' problem
От | Steve Baldwin |
---|---|
Тема | Logical replication 'possible' problem |
Дата | |
Msg-id | CAKE1Aia0KVSM0-wqE_B4ByvqU8GbPgTUT7wk2uVHZY3ov014AQ@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: Logical replication 'possible' problem
|
Список | pgsql-general |
Hi,
I'm in the process of doing the initial syncing of a subscriber with a publisher.
There is only one table that is still in a 'dumping' state. It is quite a large table and in previous executions it took several hours.
I'm not sure if it encountered a problem and stopped or if it is still going.
Looking at the replication slots on the publisher I see this:
b2bcreditonline=> select slot_name, active, active_pid from pg_replication_slots;
slot_name | active | active_pid
--------------------------------------------+--------+------------
b2bcreditonline_prod_b_master | t | 21511
b2bcreditonline_prod_b_shard | t | 21703
pg_67491625_sync_60067_7093664237039303581 | f |
(3 rows)
slot_name | active | active_pid
--------------------------------------------+--------+------------
b2bcreditonline_prod_b_master | t | 21511
b2bcreditonline_prod_b_shard | t | 21703
pg_67491625_sync_60067_7093664237039303581 | f |
(3 rows)
I assume the pg_xxxx slot is the one created for the initial copy but I'm not sure if having a false active state is normal/ok.
If it is, great. If not, how do I determine the problem and go about fixing it?
Thanks,
Steve
В списке pgsql-general по дате отправления: