Postgres Pro
Downloads
Home   >   mailing lists

Re: Postgres Stale Statistics - Mailing list pgsql-admin

From Nikhil Shetty
Subject Re: Postgres Stale Statistics
Date
Msg-id CAFpL5VxgMsRTwvvdS2WFCbmoZspLwNxWOTHMQ089ou5SjP4J8g@mail.gmail.com
Whole thread Raw
In response to RE: Postgres Stale Statistics  (Adelino Silva <adelino.silva@pt.ibm.com>)
Responses RE: Postgres Stale Statistics
List pgsql-admin
Tree view
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=31860224, u64=31860224}}], 1, -1) = 1

close(3)                                = 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) = 152

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

epoll_create1(EPOLL_CLOEXEC)            = 3

epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860176, u64=31860176}}) = 0

epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860200, u64=31860200}}) = 0

epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860224, u64=31860224}}) = 0

epoll_wait(3, [{EPOLLIN, {u32=31860224, u64=31860224}}], 1, -1) = 1

close(3)                                = 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) = 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) = 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) = 376

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

epoll_create1(EPOLL_CLOEXEC)            = 3

epoll_ctl(3, EPOLL_CTL_ADD, 11, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860176, u64=31860176}}) = 0

epoll_ctl(3, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860200, u64=31860200}}) = 0

epoll_ctl(3, EPOLL_CTL_ADD, 10, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=31860224, u64=31860224}}) = 0

epoll_wait(3, [{EPOLLIN, {u32=31860224, u64=31860224}}], 1, -1) = 1

close(3)      


Regards,

Nikhil   


On Wed, Apr 27, 2022 at 8:25 PM Adelino Silva <adelino.silva@pt.ibm.com> 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.


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
 
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.
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 <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



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

pgsql-admin by date:

Previous
From: Adelino Silva
Date:
Subject: RE: Postgres Stale Statistics
Next
From: "Capobianco, Tony"
Date:
Subject: issues connecting to RDS from psql 9.2 v 14.2