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 1njjiv-000265-W0 for pgsql-admin@arkaria.postgresql.org; Wed, 27 Apr 2022 15:37:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1njjiu-0002wi-Rs for pgsql-admin@arkaria.postgresql.org; Wed, 27 Apr 2022 15:37:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1njjiu-0002wT-6w for pgsql-admin@lists.postgresql.org; Wed, 27 Apr 2022 15:37:00 +0000 Received: from mail-vs1-xe2a.google.com ([2607:f8b0:4864:20::e2a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1njjir-0003v9-70 for pgsql-admin@lists.postgresql.org; Wed, 27 Apr 2022 15:36:59 +0000 Received: by mail-vs1-xe2a.google.com with SMTP id d2so2042711vsd.12 for ; Wed, 27 Apr 2022 08:36:57 -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=r6QEwMnH9a4BogS08JfgS2icvGqlb1573/WiFZ5EDfI=; b=AmPMWGta+Yo2e66MKvXJL0E84KD5uiItYBA2VlZ4yegzG79FU+eJ6H3Beejdvfyocd GU6ahxv25K5EBm92LV+BsRKWfrRrvI2O37XgIjBMJXImvbHg+E4muthxIC393WcpHVk4 s0MI8VJxhFyUvYxJUJro270PN2hROmSh3ktJ0KP/FxGJyIUehbW0eLXawMk0sq/a+ndd mevyBiW6c/WH7wr8XM4fCUgMkBG7WZNNWbr7S5FfslpD5DzM5/dqMmQAQfhAky1mi3F7 jf1kWSZJZXqQLXUp7/k39howDccWLXvrhDEh1zXYSOKzNrskcJd+ymnDtPiWe26C35tB yOFA== 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=r6QEwMnH9a4BogS08JfgS2icvGqlb1573/WiFZ5EDfI=; b=wuNNA6fvBs83P57MWeuToIzFQOgt8Pg2jOewXZCIMZDvir7YzeCUBJQqutPtaXZAu2 VSzlm1JEBmxpBdxbF8TmCIEBR4vix7eXYzzytCXgj5PSkgGyq0TTXqcY1ioJKknDkyGC ejcy1CdU93+3ZPDVH/Lcs98dzwkC+8rVmFtNXp9lELHDBFpd/KaytfLxp7eKoWF55HDe vgrfipUy4l976gCsgT67GMMu9ey8hPENbOib54ASArvtpoviy1UGwrp5iF+TorCl6MEx 9iQc9T8HR3ChQ2TezYzliRj2Yq5u7+Y/2rypOA8zCB5LAvT+LYLL0efRjlczAV+JbQrd 2oQQ== X-Gm-Message-State: AOAM532q843G1l+NVrO9pYwTQnmV6nG4kFTFGo8TrOYAW4qh+0h5uY0z s8vxJ0tV4dLYYYud+yf4maULRFDV98yamCen22X3NgSc1Sbpzg== X-Google-Smtp-Source: ABdhPJxPIEk+lYpFnSQVAylgMr8JIc8Frzi2vlL2p/mgNfqINGEQeylllCgl2XlWE5/CL7if6iB/ZrynAlssckyaQKg= X-Received: by 2002:a05:6102:501:b0:32c:e617:62b with SMTP id l1-20020a056102050100b0032ce617062bmr3207466vsa.9.1651073816089; Wed, 27 Apr 2022 08:36:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nikhil Shetty Date: Wed, 27 Apr 2022 21:06:44 +0530 Message-ID: Subject: Re: Postgres Stale Statistics To: Adelino Silva Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000004e579a05dda494a3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004e579a05dda494a3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Adelino, I went through the article and I see there is no issue with IPv6 in our case, it is using IPv4. I used strace and found 'Resource temporarily unavailable' error though, not sure what this means, does this mean there is an issue with disk I/O? strace: Process 5134 attached epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860224}}], 1, -1) =3D 1 close(3) =3D 0 recvfrom(10, "\2\0\0\0\230\0\0\0\7@\0\0\1\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0= \0\0"..., 1000, 0, NULL, NULL) =3D 152 recvfrom(10, 0x7ffeeb967fa0, 1000, 0, NULL, NULL) =3D -1 EAGAIN (Resource temporarily unavailable) epoll_create1(EPOLL_CLOEXEC) =3D 3 epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860176= , u64=3D31860176}}) =3D 0 epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860200, u64=3D31860200}}) =3D 0 epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860224= , u64=3D31860224}}) =3D 0 epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860224}}], 1, -1) =3D 1 close(3) =3D 0 recvfrom(10, "\2\0\0\0\250\3\0\0\7@\0\0\10\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\= 0\0\0"..., 1000, 0, NULL, NULL) =3D 936 recvfrom(10, "\2\0\0\0\250\3\0\0\0\0\0\0\10\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000, 0, NULL, NULL) =3D 936 recvfrom(10, "\2\0\0\0x\1\0\0\7@\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\= 0"..., 1000, 0, NULL, NULL) =3D 376 recvfrom(10, 0x7ffeeb967fa0, 1000, 0, NULL, NULL) =3D -1 EAGAIN (Resource temporarily unavailable) epoll_create1(EPOLL_CLOEXEC) =3D 3 epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860176= , u64=3D31860176}}) =3D 0 epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860200, u64=3D31860200}}) =3D 0 epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=3D31860224= , u64=3D31860224}}) =3D 0 epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860224}}], 1, -1) =3D 1 close(3) Regards, Nikhil On Wed, Apr 27, 2022 at 8:25 PM Adelino Silva wrote: > 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. > > > https://stackoverflow.com/questions/46008372/using-stale-statistics-inste= ad-of-current-ones > > > Using stale statistics instead of current ones - Stack Overflow > > 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 > *Sent:* Wednesday, April 27, 2022 2:49 PM > *To:* Adelino Silva > *Cc:* Pgsql-admin > *Subject:* [EXTERNAL] Re: Postgres Stale Statistics > > 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. > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > 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 > > --0000000000004e579a05dda494a3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Adelino,

I went through the article = and I see there is no issue with IPv6 in our case, it is using IPv4.
<= div>


I used strace = and found 'Resource temporarily unavailable' error though, not sure= what this means, does this mean there is an issue with disk I/O?

strace: Process 5134 attached<= /p>

epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860= 224}}], 1, -1) =3D 1

close(3)= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 0

recvfrom(10, "\2\0\0\0\230\0\0\0\7@\0\0\1\0\0\0\= 5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000, 0, NULL, NULL) =3D 152

recvfrom(10, 0x7ffeeb967fa0, 1000, 0, NULL, NULL) =3D= -1 EAGAIN (Resource temporarily unavailable)

epoll_create1(EPOLL_CLOEXEC)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 3

epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPO= LLHUP, {u32=3D31860176, u64=3D31860176}}) =3D 0

epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOL= LHUP, {u32=3D31860200, u64=3D31860200}}) =3D 0

epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPO= LLHUP, {u32=3D31860224, u64=3D31860224}}) =3D 0

epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860= 224}}], 1, -1) =3D 1

close(3)= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 0

recvfrom(10, "\2\0\0\0\250\3\0\0\7@\0\0\10\0\0\0= \1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000, 0, NULL, NULL) =3D 936

recvfrom(10, "\2\0\0\0\250\3\0\0\0\0\0\0\10\0\0\= 0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000, 0, NULL, NULL) =3D 936

recvfrom(10, "\2\0\0\0x\1\0\0\7@\0\0\3\0\0\0\0\0= \0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000, 0, NULL, NULL) =3D 376<= /p>

recvfrom(10, 0x7ffeeb967fa0, 1000, 0, NULL, NULL) =3D= -1 EAGAIN (Resource temporarily unavailable)

epoll_create1(EPOLL_CLOEXEC)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 3

epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPO= LLHUP, {u32=3D31860176, u64=3D31860176}}) =3D 0

epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOL= LHUP, {u32=3D31860200, u64=3D31860200}}) =3D 0

epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPO= LLHUP, {u32=3D31860224, u64=3D31860224}}) =3D 0

epoll_wait(3, [{EPOLLIN, {u32=3D31860224, u64=3D31860= 224}}], 1, -1) =3D 1

close(3)= =C2=A0 =C2=A0 =C2=A0=C2=A0


Regards,

<= p style=3D"margin:0px;font-stretch:normal;font-size:13px;line-height:normal= ;font-family:Menlo;color:rgb(0,0,0)">Nikhil =C2= =A0=C2=A0


On Wed, Apr 27, 2022 at 8:25 PM Adelino Si= lva <adelino.silva@pt.ibm.co= m> wrote:
One possible cause for this problem is that the statistics collector proces= s is bound to an IP:port which is not responding.
See the following thread discussion.

3D""
Teams. Q&A for work. Connect and share knowledge within a single locati= on that is structured and easy to search. Learn more

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
=C2=A0
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 S= ilva <adel= ino.silva@pt.ibm.com> wrote: Hi, Found this thread that explains the= warning.
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
=C2=A0
ZjQcmQRYFpfptBannerEnd
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 n= ot responding

3D""
Po= stgreSQL: 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 t= he intratubes on this. > =E2=80=A6
www.postgresql.org<= /a>


Regards,

Adelino Silva

From: 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

--0000000000004e579a05dda494a3--