Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nji3V-0004uM-Jk for pgsql-admin@arkaria.postgresql.org; Wed, 27 Apr 2022 13:50:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nji3U-0004jo-Ik for pgsql-admin@arkaria.postgresql.org; Wed, 27 Apr 2022 13:50:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nji3U-0004je-4m for pgsql-admin@lists.postgresql.org; Wed, 27 Apr 2022 13:50:08 +0000 Received: from mail-vs1-xe2b.google.com ([2607:f8b0:4864:20::e2b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nji3R-000728-49 for pgsql-admin@lists.postgresql.org; Wed, 27 Apr 2022 13:50:07 +0000 Received: by mail-vs1-xe2b.google.com with SMTP id w124so1741393vsb.8 for ; Wed, 27 Apr 2022 06:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hiqBpkoctKLKMtNQiR9iaRVr7PUtmPM5piV8NnL+ICU=; b=cPpXy0fFGSR6BUZ+HyHXt3jHqDgNLE6iCzD0edW4YEtfmBT8O5OB5Sm0ac7iWU6LEm nh4FukLGsMVbP8DIRAOSC+TlWakHahIxZ2dvPRHT29oApuebov2+5S2hlb3iYJ+tWG7K 0x0fLwdEGfC45zc66/M5IO8+uaFbdEBMbdGxpGv1VJzCAKiSRvhHIcgS2NeVkR8CQrlI Vv8NtJQxojMkADMoMmVFnuwR33QWjpBHkFEpe1v6tV1zs6NvpeXWitXyP8j/uA2ZWzBK B8QJ93ST5ooO1XUAlft0ym7m8+NItr19IyaVqjGcSd6h0uB/GYIEONrG77M8h33io+gT meMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hiqBpkoctKLKMtNQiR9iaRVr7PUtmPM5piV8NnL+ICU=; b=S1UTjprRjjTy2iYfSJp33a09coqEUJ+i5gmn/ZrXJRKun9PEKs6KNKq6Pf3o0Xn6lN gxAKwpNwnJ2/2BlnfAbfrZc61WJe+pngegha/hg/8Hhs0lUU3S917NF5IiHlpMuqXI6X TEwOQRqJl1+PAHRcqOJRiWUmzCc1X0D1lYfafpZJ7kG7ki3Q5t0e5w1M7rlogtehHe8n nft5TCwXGOcvNIr+wSlwQIg6Kqa4t0RbFYqU5nF/PmeQ4MfJnK5dN0YgWYNauraK71Wd z4yPn9/7QZ9gAYwpwsmI5lmBDGYjyjIinPXwfdvYrZJBSwSlNZqyVfiJqsJFgC/yqccv U8/Q== X-Gm-Message-State: AOAM531AUpedGuNBBMZTfM6YKjdqLo7bPD9MKTov447B2z1VJLw7d2ct 3JvcurCUCAXgAmuQ+WvXzHvlaZXLf/DDsjnok+o= X-Google-Smtp-Source: ABdhPJxueW5KhxveFzseRawcXrZNYWJfcmUlrJxe2SoR209/lu/D58WHJPOlZq0gKkCmdAtxUTjjzqS7rpOe1qECfss= X-Received: by 2002:a05:6102:955:b0:32c:ef80:ba7f with SMTP id a21-20020a056102095500b0032cef80ba7fmr1958026vsi.17.1651067403209; Wed, 27 Apr 2022 06:50:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nikhil Shetty Date: Wed, 27 Apr 2022 19:19:51 +0530 Message-ID: Subject: Re: Postgres Stale Statistics To: Adelino Silva Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000011919305dda3167a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000011919305dda3167a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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/1457523467.24545.43.camel@2ndquadra= nt.com > > > PostgreSQL: Re: using stale statistics instead of current ones because > stats collector is not responding > > Hi, On Tue, 2016-03-08 at 16:18 -0800, Tory M Blue wrote: > No hits on th= e > intratubes on this. > =E2=80=A6 > www.postgresql.org > > > Regards, > > Adelino Silva > > ------------------------------ > *From:* Nikhil Shetty > *Sent:* Wednesday, April 27, 2022 12:08 PM > *To:* Pgsql-admin > *Subject:* [EXTERNAL] Postgres Stale Statistics > > Hi, We are getting below WARNING on one of the standby instances. Not sur= e > what caused it but to resolve it we tried restarting the database instanc= es > 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 instanc= es > 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 > --00000000000011919305dda3167a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Adelino,

I had gone through that thr= ead 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 n= ot responding

3D""
PostgreSQL: Re: using stale sta= tistics instead of current ones because stats collector is not responding
Hi, On Tue, 2016-03-08 at 16:18 -0800, Tory M Blue wrote: > No hits on t= he intratubes on this. > =E2=80=A6
www.postgresql.org<= /a>


Regards,

Adelino Silva

Fro= m: Nikhil Shetty <nikhil.dba04@gmail.com>
Sent: Wednesday, April 27, 2022 12:08 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Postgres Stale Statistics
=C2=A0
Hi, We are getting below=C2=A0WARNING=C2=A0on 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 ins= tead of current ones because
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
=C2=A0
ZjQcmQRYFpfptBannerEnd
Hi,

We are getting below=C2=A0WARNING=C2=A0on one of the standby instances. Not= sure what caused it but to resolve it we tried restarting the database ins= tances but it is still not working


WARNING - using stale statistics instead of current ones because stats coll= ector is not responding


Postgresql version - 11.7


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


Thanks and Regards,

Nikhil

--00000000000011919305dda3167a--