Hi Chris,
On Mon, Jul 26, 2010 at 10:03:15AM +1000, Chris wrote:
So I'd be better off making these 2 match?
sql_refresh_time: 60
sql_history: 5m
Correct.
For what it's worth the log seems to be aggregated on the history time.
I only see the 5 min increments when I run pmpgplay in debug
Hi Paolo,
For what it's worth the log seems to be aggregated on the history time.
I only see the 5 min increments when I run pmpgplay in debug mode.
Yes, this is because you get logged down the exact tuple that was going
to be written to the database. And records in the database are fitted in
Hi,
The 'failsafe' mechanism (ie. writing to a backup database or to log
files) kicks in upon receipt of an error code from the RDBMS API. So
what you see in the log file should never be already in the database.
Excellent, thanks.
Your specific configuration is tricky because you write to
Hi Chris,
The 'failsafe' mechanism (ie. writing to a backup database or to log
files) kicks in upon receipt of an error code from the RDBMS API. So
what you see in the log file should never be already in the database.
Your specific configuration is tricky because you write to the RDBMS
every 60
Hi,
I'm using pmacct-0.12.0rc3 with postgresql.
I've been trying to work out what pmpgplay does when it looks at a log
file. I couldn't find much in my searches that go into the details of
how it does things.
It seems it generates a bunch of sql, but does it check to see if that
record
