Re: Postgres Stale Statistics

Hi,

Found this thread that explains the warning.
using stale statistics instead of current ones because stats collector is not responding
https://www.postgresql.org/message-id/1457523467.24545.43.camel@2ndquadrant.com
[https://www.postgresql.org/media-archives/img/about/press/elephant.png]<https://www.postgresql.org/message-id/1457523467.24545.43.camel@2ndquadrant.com>
PostgreSQL: Re: using stale statistics instead of current ones because stats collector is not responding<https://www.postgresql.org/message-id/1457523467.24545.43.camel@2ndquadrant.com>
Hi, On Tue, 2016-03-08 at 16:18 -0800, Tory M Blue wrote: > No hits on the intratubes on this. > …
www.postgresql.org

Regards,

Adelino Silva

________________________________
From: Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
Sent: Wednesday, April 27, 2022 12:08 PM
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: [EXTERNAL] Postgres Stale Statistics

Hi, We are getting below WARNING on one of the standby instances. Not sure what caused it but to resolve it we tried restarting the database instances but it is still not working WARNING - using stale statistics instead of current ones because
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd
Hi,

We are getting below WARNING on one of the standby instances. Not sure what caused it but to resolve it we tried restarting the database instances but it is still not working

WARNING - using stale statistics instead of current ones because stats collector is not responding

Postgresql version - 11.7

Any other option to resolve this? We are thinking of building the standby again but what if the WARNING is for a primary database instance and a restart won't solve it?

Thanks and Regards,

Nikhil