Hi Sergio, It looks those processes are locked out of the table they want to write to. In MySQL you can check this kind of stuff with a "SHOW PROCESSLIST"; the PostgreSQL equivalent should be "SELECT * FROM pg_stat_activity". Its output might very well shed some light.
Just btw, the number of pmacct processes allowed to queue up is settable via the sql_max_writers configuration directive. Cheers, Paolo On Thu, May 13, 2010 at 10:04:14AM -0300, Sergio Charpinel Jr. wrote: > Hi, > > After less than one day running pmacct, my database grew from 1.5G to 15G. > At this point I get a lot of postmaster and nfacctd process, and none of > them seems to be using CPU and not writting in DB. > > 6774 root 15 0 160m 103m 916 S 0.0 0.9 0:04.04 nfacctd > 6775 postgres 15 0 2210m 1.3g 1.3g S 0.0 11.8 0:31.50 postmaster > 6784 root 15 0 160m 103m 916 S 0.0 0.9 0:04.19 nfacctd > 6785 postgres 16 0 2210m 1.1g 1.1g S 0.0 9.9 0:23.77 postmaster > 6794 root 15 0 160m 103m 916 S 0.0 0.9 0:02.81 nfacctd > 6795 postgres 15 0 2210m 1.1g 1.1g S 0.0 9.4 0:20.57 postmaster > 6804 root 15 0 160m 103m 916 S 0.0 0.9 0:02.04 nfacctd > 6805 postgres 16 0 2210m 870m 867m S 0.0 7.4 0:14.03 postmaster > 6819 root 15 0 160m 103m 916 S 0.0 0.9 0:02.64 nfacctd > 6820 postgres 15 0 2210m 816m 813m S 0.0 7.0 0:13.14 postmaster > 6829 root 15 0 160m 103m 916 S 0.0 0.9 0:01.17 nfacctd > 6830 postgres 15 0 2210m 625m 622m S 0.0 5.3 0:09.63 postmaster > 6861 root 15 0 160m 103m 916 S 0.0 0.9 0:01.28 nfacctd > 6862 postgres 15 0 2210m 558m 556m S 0.0 4.8 0:08.16 postmaster > 6889 root 15 0 160m 103m 916 S 0.0 0.9 0:00.33 nfacctd > 6890 postgres 16 0 2210m 269m 267m D 0.0 2.3 0:03.16 postmaster > > [ ... ] _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
