From: Benjamin Krajmalnik <kraj@illumen.com>
To: Ben K. <bkim@coe.tamu.edu>
To: pgsql-admin@postgresql.org
Subject: Re: New system recommendations
Date: Fri, 28 Apr 2006 08:35:52 -0600
Message-ID: <8511B4970E0D124898E973DF496F9B432515DE@stash.stackdump.local> (raw)
The stored procedure is a plpgsql function which gets passed parameters
from the monitoring agent.
It then dynamically creates a device record for the monitored device if
one does not yet exist.
Once that is done it creates a test record for the particular test if
one does not exist.
Once that is done, it aggregates dynamically the data into 4 tables - a
daily snapshot, a weekly snapshot, and a monthly snapshot, and a
dashboard snapshot.
Once all of that has been accomplished, it creates a raw log entry
(which as of next week will go to a given partition). This data goes
into the partitioned table to facilitate purging of retention periods
without hammering at the database and having to rebalance indices (I
just truncate the partition once it is no longer needed).
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Ben K.
Sent: Thursday, April 27, 2006 9:19 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] New system recommendations
> Record insertion is done via an ODBC call to a stored procedure from a
> Windows based host monitor"
I wondered what this stored procedure was (is it a function or something
outside postgresql).
There was an interesting article on odbc - that application code can
make
big differences in database related performance.
http://ourworld.compuserve.com/homepages/Ken_North/ODBCPERF.HTM
Thought odbc performance might be also a thing to consider but this
article seemed to attest otherwise. Hence the question.
Regards,
Ben K.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kraj@illumen.com, bkim@coe.tamu.edu
Subject: Re: New system recommendations
In-Reply-To: <8511B4970E0D124898E973DF496F9B432515DE@stash.stackdump.local>
References: <8511B4970E0D124898E973DF496F9B432515DE@stash.stackdump.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox