![]() Or on another host where it is bound to IPv6 ("udp6"): # netstat -n -u -pĪctive Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name The output is something like this: Active Internet connections (w/o servers) You can check to which IP and UDP port the "postmaster" (or "postgres") service is bound with netstat -n -u -p If the socket it had seleccted was IPv6 and it is later disabled, it stops working and you get that message in the logs. Localhost], create a UDP socket and test it until it has a socket PostgreSQL will loop through all the addresses returned [for I came across a detailed explanation here (search for "The statistics collector" in the page), but in short: This happened to me when I disabled IPv6 on the server without restarting Postgres. I've tried to stop it, and it doesn't helps. I had a never ending process connected to the db. ![]() When this is running, the VACUUM FULL VERBOSE ANALYZE seems blocked.Ĭan that never ending process be the root causes of my problem? In that case, since I need to have that proccess running, do I have to tweak something on the server? ![]() I have a never ending proccess connected to the database.VACUUM FULL VERBOSE ANALYZE doesn't helps.P.S: I fully understand that's not a severe error, but it floods my logs, and I have the fear to not see important messages. I have also tried to tweak the nf parameters as follows I have 32Gb RAM, and in routine ~ 500Mb are used.I have 4 CPU, and in routine less than 5% of 1 CPU is used.What's the meaning of this? How can I solve that?Īdditional information based on Greda's reply: Using stale statistics instead of current ones because stats collector is not respondingĮxcept a post on serverfault which is not helpfull and seems related to standby databases setup (which is not my case), I don't find anything to solve this. My postgresql 9.5 logs shows every minute the message:
0 Comments
Leave a Reply. |