3

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?

1
  • 3
    Is replication still working? Look at the standby logs. Perhaps you broke replication, and WAL has to be retained until you fix it. Commented Aug 14, 2020 at 11:20

1 Answer 1

1

I'm still unsure what caused the issue, but probably it was adding a new column. After restoring a backup and recreating publication and subscription everything worked pretty good.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.