I have a postgres table (300Mb size) which is logically replicated to another server. Until I've made some changes everything was perfectly good. Then master started to grow (up to 2,5 Gb at rate 15 mb at 5 minutes roughly). I tried to tune WAL settings and do a WAL cleanup, but it didn't help.
What I have done before this issue was discovered:
Rebuilt a materialized view dependent on master table a lot of times (and it is a heavy CPU consuming operation)
Added a new column on master table and slave table
Added a rule on inserts (copy a value from jsonfield to charfield)
What could have caused this issue?