public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nikhil Shetty <[email protected]>
To: Adelino Silva <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Postgres Stale Statistics
Date: Wed, 27 Apr 2022 19:19:51 +0530
Message-ID: <CAFpL5VzrX4To00Qv8xyQJsaJ+0gc7y4bY7pUWbg7Ffh47ZVuYA@mail.gmail.com> (raw)
In-Reply-To: <SA0PR15MB3856E1C18660DE3F01942DAED2FA9@SA0PR15MB3856.namprd15.prod.outlook.com>
References: <CAFpL5VzjDi35wo3+P19+kc7wGPh5=Xc-kCUfNDoTg3xNrcHnCw@mail.gmail.com>
	<SA0PR15MB3856E1C18660DE3F01942DAED2FA9@SA0PR15MB3856.namprd15.prod.outlook.com>

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 <[email protected]>
wrote:

> 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/[email protected]
>
> <https://www.postgresql.org/message-id/[email protected];
> PostgreSQL: Re: using stale statistics instead of current ones because
> stats collector is not responding
> <https://www.postgresql.org/message-id/[email protected];
> 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 <[email protected]>
> *Sent:* Wednesday, April 27, 2022 12:08 PM
> *To:* Pgsql-admin <[email protected]>
> *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
>

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Postgres Stale Statistics
  In-Reply-To: <CAFpL5VzrX4To00Qv8xyQJsaJ+0gc7y4bY7pUWbg7Ffh47ZVuYA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox