Re: huge price database question..

From: Andy Colson <andy(at)squeakycode(dot)net>
To: Brent Wood <Brent(dot)Wood(at)niwa(dot)co(dot)nz>
Cc: Jim Green <student(dot)northwestern(at)gmail(dot)com>, David Kerr <dmk(at)mr-paradox(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: huge price database question..
Date: 2012-03-21 03:14:21
Message-ID: 4F69478D.5080609@squeakycode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/20/2012 08:54 PM, Brent Wood wrote:
>
> Also look at a clustered index on timestamp
>
>
> Brent Wood
>
> GIS/DBA consultant
> NIWA
> +64 (4) 4 386-0300

A clustered index is only "clustered" at the point in time you run the command. It wont remain that way, and with a really big table, you don't wanna spend the time re-clustering it every time you import more data.

-Andy

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Kerr 2012-03-21 03:24:22 Re: huge price database question..
Previous Message Andy Colson 2012-03-21 03:01:01 Re: huge price database question..