Re: index organized tables use case

From: "Isak Hansen" <isak(dot)hansen(at)gmail(dot)com>
To: "Enrico Sirola" <enrico(dot)sirola(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: index organized tables use case
Date: 2007-12-12 14:43:30
Message-ID: 6b9e1eb20712120643k6599d6f8k88ac1bbee1391152@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/12/07, Enrico Sirola <enrico(dot)sirola(at)gmail(dot)com> wrote:
> Hello Isak,
>
> Isak Hansen ha scritto:
>
> > Have a look at the cluster operation;
> > <http://www.postgresql.org/docs/8.3/static/sql-cluster.html>.
> >
> > AFAIK it does lock & duplicate the whole table during reordering,
> > which may or may not be an issue for you.
>

Sorry Enrico and list, the respond-to setting on this list gets me every time..

> thanks for the reply; I was aware about this option, anyway I think
> probably it won't be practical: the table is very big and this exclusive
> lock would probably be a pain. I think probably I will start with the
> present relation and then redesign the application at a second stage

This is a long shot, but if the table is huge you could also consider
partitioning. That really depends on the contents of 'code', though..

See <http://www.postgresql.org/docs/8.3/static/ddl-partitioning.html>.

Isak

> Thanks,
> e.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2007-12-12 14:48:16 Re: Slow PITR restore
Previous Message smiley2211 2007-12-12 14:14:56 Re: Trigger - will not perform INSERT