"Time of latest checkpoint" stays too old on both master and slave

From: rihad <rihad(at)mail(dot)ru>
To: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: "Time of latest checkpoint" stays too old on both master and slave
Date: 2019-06-30 06:49:27
Message-ID: 86255d9c-51b0-aca3-1757-016952c73c67@mail.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Current time is 10:44. pg_controldata shows on both on master & slave
server which uses streaming replication:

Time of latest checkpoint:            Sun Jun 30 07:49:18 2019

So it was almost 3 hours ago. There are always some heavy writes and a
new WAL file in the pg_wal/ directory is created every few minutes.
checkpoint_timeout is 20min so it should have triggered long ago.

checkpoint_timeout = 20min #5min                # range 30s-1d
max_wal_size = 8GB
min_wal_size = 80MB
checkpoint_completion_target = 0.9

hot_standby is enabled on the slave, hot_standby_feedback is off not to
bloat the master,

hot_standby_streaming_delay is 30min.

Experiencing this long delay after the upgrade (via dump/restore) from
PG 9.6 to 11.4.

Thanks for any tips.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message rihad 2019-06-30 06:59:06 Re: "Time of latest checkpoint" stays too old on both master and slave
Previous Message Hans Schou 2019-06-30 06:04:44 Re: Memory settings