RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
От | Hayato Kuroda (Fujitsu) |
---|---|
Тема | RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine |
Дата | |
Msg-id | OSCPR01MB14966BC4A92741FA20F44D161F538A@OSCPR01MB14966.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine (Thadeus Anand <thadeus@rmkv.com>) |
Ответы |
Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
|
Список | pgsql-bugs |
Dear Thadeus, Nantha, > Can these spill files in the pg_replslot folder be deleted safely, if all the subscribers have > caught up? Do not remove them manually. Spill files exist because the logical replication system considers they are needed. I cannot know your system well, but in your first example, there is a possibility that transaction 10861356 is not committed yet thus walsender keep decoding and spilling. Actually it looks for me that subscribers have not been caught up. Removing them may cause unexpected behavior. > (I noticed last night when I restarted my publisher, the spill files were removed > automatically) When postmaster restarts, it checks all directory under pg_replslot and removes all .spill files. This is harmless because spilled changes would be decoded again. > Can I use ALTER SUBSCRIPTION to set streaming on, with my existing subscriptions? Yes, you can. More detail, after you run ALTER SUBSCRIPTION command, the apply worker on the subscriber restarts and establishes the connection again with the different streaming parameter. Note that pg_stat_activity (with the pid) is still needed to understand the issue correctly. Best regards, Hayato Kuroda FUJITSU LIMITED
В списке pgsql-bugs по дате отправления: