On 05/14/2010 12:15:27 PM, Paolo Lucente wrote: > Hi Sergio, > > On Fri, May 14, 2010 at 10:58:00AM -0300, Sergio Charpinel Jr. wrote: > > > I couldnt get any useful information from this command. > > I get no erros in postgresql, nfacctd and pmacctd log files. > > I would expect you to see a "Maximum number of SQL writer processes > reached" message in the logs. I will do some checks and let you know. > > > Data is still being written in DB, but I'm suspecting that some are > being > > lost. Because my database grew just 5G/day after that.
It occurs to me that some of this may have to do with postgresql table vacuuming and the autovacuum process. I've had problems in the past when initially loading data into large tables before the first vaccuming/analyze was done. It would take some time before things stabilized. My technique was to "pause" data loading and do a vacuum analyze every now and then. This is probably not feasible. I can imagine there could be situations where data is loaded fast enough to trigger autovacuums that don't have enough time to finish so you get multiple processes running. If you are also deleting data this would explain the database size/growth mis-match, because the deleted data has not yet been recovered. It's a thought. Karl <[email protected]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
