[rrd-developers] RRD PostgreSQL extension

[Dustin Fisch]

Hi,

> as fahr as I understand it, the extension would sit in the server,
> this means the BLOB would remain where it is ...
Right.

Expecting, there would be a SQL function like "rrd_update(OID
rrd_file, DOUBLE value)", the data transmitted over the network for
such a function call are a the 4 bytes for the value, the 8 bytes for
the OID, a few bytes for the function name and the overhead for the
transaction.

> > Also it's no big deal to organize the history table alongside
> > with the last value, and let the SQL engine handle the data in a
> > traditional way.
RRD provides some features, which are hard to implement in classical
SQL, like bucketing, consolidation of older data and some other cool
stuff. Even aggregation like MIN and MAX per time bucket is faster in
RRD than in PostgreSQL.

cheers
fooker

Tobias Oetiker <tobi at oetiker.ch> wrote:

> Hi Stan,
> 
> Yesterday Stanislav Sinyagin wrote:
> 
> > how is it supposed to handle large RRD files over the network?
> > If, say, the client and server are on different hosts, and you're
> > updating RRD data in a BLOB. and RRD data can easily be several
> > megabytes. So, how is the data transfer supposed to be organized?
> > I have a feeling that you're going to transfer the whole file
> > over the network, probably more than once per update.
> >
> > Also it's no big deal to organize the history table alongside
> > with the last value, and let the SQL engine handle the data in a
> > traditional way.
> 
> as fahr as I understand it, the extension would sit in the server,
> this means the BLOB would remain where it is ...
> 
> cheers
> tobi
> 


-- 
http://lab.sh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
Url : http://lists.oetiker.ch/pipermail/rrd-developers/attachments/20120912/f4c03d4a/attachment.pgp