On Sat, Jan 13, 2007 at 06:35:20PM -0500, [EMAIL PROTECTED] wrote:
> I guess that's the trick, to have the "current" or at least "recent"
> database and then the historical one. As of now, the process of polling
> the 17 machines takes about 40 seconds or so (when I first started running
> the
Hi Jonathan,
Splitting and automatic updating of history via triggers isn't
very complicated.
BEGIN TRANSACTION;
CREATE TABLE StatsCurrent (
MachineVARCHAR(16) NOT NULL,
Load REAL,
ScratchCHAR(4),
MemINTEGER,
MemPctFree INTEGER,
I'm gonna cut all the content and say just one thing.
If Sqlite supported table partitioning this would be piece of cake without any
complications.
http://www.postgresql.org/docs/8.2/static/ddl-partitioning.html
--
It's time to get rid of your current e-mail client ...
... and start using
On 1/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Jay:
The closer to real-time, the better. The most often a cron job can run
under Linux is minutely, and minutely is pretty good. I guess I could
have the summary process occur at the end of the script that polls the
machines. It
First off, thanks for the help and sorry for the formatting of the
message. I didn't know how it was going to turn out and I probably was
overly optimistic as well as too verbose.
Secondly, as I feared, seems like it was an XY question, so sorry for that
as well.
I'll address the two replies
5 matches
Mail list logo
