pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Hans Guijt <hg@terma.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Less intrusive ways to cluster?
Date: Tue, 08 Jan 2008 08:49:08 -0800
Message-ID: <4783A984.10602@commandprompt.com> (raw)
In-Reply-To: <85978993146E1A4AA9CC4B2945CAFC940233AD76@exch-be.terma.com>
References: <85978993146E1A4AA9CC4B2945CAFC940233AD76@exch-be.terma.com>

Hans Guijt wrote:
> I have a fairly large table that keeps track of data measured by our
> system. The data is in the form of BLOBs, and is only queried in order
> of timestamp. Because we are measuring from multiple devices, the data
> does not necessarily arrive in the database in correct temporal order,
> and in fact it is very well possible for corrections to some BLOBs to be
> entered after measurement. As a result, there is considerable churn in
> the table - but only at the very end, in the last hour or so of data.
> Older data is normally left alone.

> Alternatively, is there some way to do partial clustering? Since 99% of
> my data set will already be properly clustered, except for the last 24
> hours or so of data, just clustering that last bit (which is trivial by
> comparison) would already help a great deal. However, I'm not sure how
> to achieve this. 

Why not break it up into a partitioning scheme?

Joshua D. Drake

> 




view thread (2+ messages)

Message-ID: <4783A984.10602@commandprompt.com>
Permalink:  ../4783A984.10602@commandprompt.com/
Also on:    postgresql.org/message-id/4783A984.10602@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, hg@terma.com
  Subject: Re: Less intrusive ways to cluster?
  In-Reply-To: <4783A984.10602@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox