Fixed a problem with 100% CPU stuck after the PostgreSQL service started

  • 2020-05-06 11:52:05
  • OfStack

There are N postgres.exe in the process (this is normal, see the official documentation), but one is always full of CPU (50% of the resources because the machine is dual-core). The native pgAdmin III connection will die.

A search on the Internet failed to find the answer.

Looking at the log, there is an error message:

%t LOG:   could not receive data from client: An operation was attempted on something that is not a socket.

, according to the error in HP website found the answer (should be win problems, but I found the answer here, is very interesting) (http: / / h10025. www1. hp. com/ewfrf/wc/document? docname = c00724449 & lc = zh - hans & dlc = zh & cc = tw & product = 86191 & lang = zh) :

Step 1: reset Winsocks  
Resetting the Winsock layer allows the browser to find the page using URL. Use the following sections according to your version of Windows.
Installed with Windows XP Service Pack 2 or higher computer
If you have Windows XP Service Pack 2 or later installed, follow the steps in this section. If Service Pack 2 is not installed, skip to step 2.
Click start, and then click run.
In the open TAB, type: netsh winsock reset
Click ok and restart the computer.
Open cmd, run netsh winsock reset, restart the computer, troubleshoot!

Related articles: