Re: Best way to handle multi-billion row read-only table?

From: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Asher <asher(at)piceur(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: Best way to handle multi-billion row read-only table?
Date: 2010-02-10 16:40:25
Message-ID: 3eff28921002100840k7bd84c4avd296d2ee8287271e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/2/10 Greg Stark <gsstark(at)mit(dot)edu>:
> On Wed, Feb 10, 2010 at 2:32 PM, Asher <asher(at)piceur(dot)co(dot)uk> wrote:
>> The data will initially be accessed via a simple GUI which will allow
>> browsing over a subset of the data (subsampled down to 1 sample/minute/hour,
>> etc.
>
> It sounds like you could use a tool like rrd that keeps various levels
> of aggregation and intelligently chooses the right level for the given
> query. I think there are such tools though I'm not sure there are any
> free ones.

Use as much memory as possible to fit indexes as well as portions of
the table space itself in RAM.
Of course, poor indexing can kill any effort.

--
Vincenzo Romano
NotOrAnd Information Technologies
NON QVIETIS MARIBVS NAVTA PERITVS

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2010-02-10 16:46:19 Re: need clean way to copy col vals from one rec to another
Previous Message Gauthier, Dave 2010-02-10 16:28:55 need clean way to copy col vals from one rec to another