RE: Postgres Stale Statistics
One possible cause for this problem is that the statistics collector process is bound to an IP:port which is not responding.
See the following thread discussion.
 | Teams. Q&A for work. Connect and share knowledge within a single location that is structured and easy to search. Learn more stackoverflow.com |
Regards,
Adelino Silva
From: Nikhil Shetty <nikhil.dba04@gmail.com>
Sent: Wednesday, April 27, 2022 2:49 PM
To: Adelino Silva <adelino.silva@pt.ibm.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Re: Postgres Stale Statistics
Sent: Wednesday, April 27, 2022 2:49 PM
To: Adelino Silva <adelino.silva@pt.ibm.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Re: Postgres Stale Statistics
This Message Is From an External Sender
This message came from outside your organization.
Hi Adelino,
I had gone through that thread before, we cannot move the stats to RAM as of now.
Thanks,
Nikhil
On Wed, Apr 27, 2022 at 6:16 PM Adelino Silva <adelino.silva@pt.ibm.com> wrote:
Hi,Found this thread that explains the warning.using stale statistics instead of current ones because stats collector is not responding
Sent: Wednesday, April 27, 2022 12:08 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Postgres Stale StatisticsThis Message Is From an External SenderThis message came from outside your organization.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
В списке pgsql-admin по дате отправления: