cvs tip - stats buffer process consuming 100% cpu
От | Joe Conway |
---|---|
Тема | cvs tip - stats buffer process consuming 100% cpu |
Дата | |
Msg-id | 43BAD231.3010505@joeconway.com обсуждение исходный текст |
Ответы |
Re: cvs tip - stats buffer process consuming 100% cpu
|
Список | pgsql-hackers |
I just noticed that the stats buffer process is consuming 100% cpu as soon as a backend is started, and continues after that backend is ended: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15150 postgres 25 0 27004 948 508 S 99.9 0.0 0:30.97 postmaster # ps -ef |grep 15150 postgres 15150 15143 78 11:29 pts/3 00:00:38 postgres: stats buffer process postgres 15151 15150 0 11:29 pts/3 00:00:00 postgres: stats collector process (gdb) bt #0 0x000000383b8c2633 in __select_nocancel () from /lib64/libc.so.6 #1 0x000000000055e896 in PgstatBufferMain (argc=Variable "argc" is not available. ) at pgstat.c:1921 #2 0x000000000055f73b in pgstat_start () at pgstat.c:614 #3 0x0000000000562fda in reaper (postgres_signal_arg=Variable "postgres_signal_arg" is not available. ) at postmaster.c:2175 #4 <signal handler called> #5 0x000000383b8c2633 in __select_nocancel () from /lib64/libc.so.6 #6 0x0000000000560d0f in ServerLoop () at postmaster.c:1180 #7 0x0000000000562443 in PostmasterMain (argc=7, argv=0x88df20) at postmaster.c:943 #8 0x00000000005217fe in main (argc=7, argv=0x88df20) at main.c:263 I noticed a recent discussion on the stats collector -- is this related to a recent change? Joe
В списке pgsql-hackers по дате отправления: