Tobias Oetiker wrote:
> Today Dustin Fisch wrote:
>
> > > Not sure how you are going to handle multiple datasources in a
> > > single RRD in your trigger, but I'm sure you have an idea.
> >
> > Anthony Johnson wrote:
> >
> > > Not sure how you are going to handle multiple datasources in a
> >
Today Dustin Fisch wrote:
> > Not sure how you are going to handle multiple datasources in a single
> > RRD in your trigger, but I'm sure you have an idea.
>
> Anthony Johnson wrote:
>
> > Not sure how you are going to handle multiple datasources in a single
> > RRD in your trigger, but I'm sure
> Not sure how you are going to handle multiple datasources in a single
> RRD in your trigger, but I'm sure you have an idea.
Anthony Johnson wrote:
> Not sure how you are going to handle multiple datasources in a single
> RRD in your trigger, but I'm sure you have an idea. Another
> table(data
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 byt
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
sch
> To: Anthony Johnson
> Cc: rrd-developers@lists.oetiker.ch
> Sent: Wednesday, September 12, 2012 5:32 AM
> Subject: Re: [rrd-developers] RRD PostgreSQL extension
>
> Hm. Also a nice idea.
>
> But the benefit I want to from the PostgreSQL extension is to use psql
&
Not sure how you are going to handle multiple datasources in a single
RRD in your trigger, but I'm sure you have an idea. Another
table(datasource) could be used via a foreign key with your trigger
located there.
That said... I am also inspired:-)
I am going to create a RRD FUSE FS prototype tha
Hm. Also a nice idea.
But the benefit I want to from the PostgreSQL extension is to use psql
as a network protocol and feeding the RRD database from data I have in
my PostgreSQL database.
The idea is to have a table with the following columns:
id BIGSERIAL,
name VARCHAR,
value DOUBLE,
history RRD
Just curious... couldn't you simply build or use one of the existing
Database filesystems that work with Fuse? Then you could mount a
filesystem whose backend is Postgres.
http://sourceforge.net/apps/mediawiki/fuse/index.php?title=DatabaseFileSystems
The postgres FUSE project seems to be dead,
Tobias Oetiker wrote:
> Hi Dustin,
>
> Yesterday Dustin Fisch wrote:
>
> > Hi,
> >
> > I am currently thinking about building an RRD extension for
> > PostgreSQL.
> >
> > The extension will provide a RRD data type which represents a
> > complete database and functions for all the existing fun
Hi Dustin,
Yesterday Dustin Fisch wrote:
> Hi,
>
> I am currently thinking about building an RRD extension for PostgreSQL.
>
> The extension will provide a RRD data type which represents a
> complete database and functions for all the existing functions of the
> RRD tool, like create, update, fir
Hi,
I am currently thinking about building an RRD extension for PostgreSQL.
The extension will provide a RRD data type which represents a
complete database and functions for all the existing functions of the
RRD tool, like create, update, first and graph...
PostgreSQL has a nice API for LOB, whi
12 matches
Mail list logo
