Skip site navigation (1) Skip section navigation (2)

Re: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...

From: Robert Treat <rob(at)xzilla(dot)net>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...
Date: 2011-02-28 22:35:28
Message-ID: AANLkTik57s6pAfRaMT85yW4Jsrjv+rxJ_mBF-+K=m-2i@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Feb 28, 2011 at 4:13 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Mon, Feb 28, 2011 at 6:31 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> What's needed here is for someone to write a good mrtg/rrd/whatever
> replacement using postgres as its data store. If you're monitoring
> something sensitive then you would store the data in a *different*
> postgres server to avoid Tom's complaint. There may be aspects of the
> job that Postgres does poorly but we can focus on improving those
> parts of Postgres rather than looking for another database. And
> frankly Postgres isn't that bad a tool for it -- when I did some
> performance analysis recently I actually ended up loading the data
> into Postgres so I could do some of the aggregations using window
> functions anyways.
>

Greg, see https://labs.omniti.com/labs/reconnoiter, but also see
Josh's nearby email about how he's trying to solve this internal to
the database.


Robert Treat
play: xzilla.net
work: omniti.com
hiring: l42.org/Lg

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-02-28 22:41:02
Subject: Re: Sync Rep v17
Previous:From: Kevin GrittnerDate: 2011-02-28 22:28:22
Subject: Re: Native XML

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group