"Time of latest checkpoint" stays too old on both master and slave - Mailing list pgsql-general

From rihad
Subject "Time of latest checkpoint" stays too old on both master and slave
Date
Msg-id 86255d9c-51b0-aca3-1757-016952c73c67@mail.ru
Whole thread Raw
Responses Re: "Time of latest checkpoint" stays too old on both master andslave
List 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.




pgsql-general by date:

Previous
From: Hans Schou
Date:
Subject: Re: Memory settings
Next
From: rihad
Date:
Subject: Re: "Time of latest checkpoint" stays too old on both master andslave